| 1 |
Peter Humphrey wrote: |
| 2 |
> On Sunday 11 October 2009 22:23:11 Alan McKinnon wrote: |
| 3 |
> |
| 4 |
> |
| 5 |
>>> I knew how to do it but I thought it would return a lot of hits from |
| 6 |
>>> anything containing the letter "q". Later on when I had a little bit of |
| 7 |
>>> time to sit here, I tried it. It only returned the one result. Still |
| 8 |
>>> sort of surprised about that. I actually just ran equery b q . Neato |
| 9 |
>>> ! It has a microscope and read my mind. o_O |
| 10 |
>>> |
| 11 |
>> which doesn't accept regular expressions or wild-cards, it wants a literal |
| 12 |
>> value. The man page says it will return the path used if the exact argument |
| 13 |
>> is entered on the command line. So you can only get one answer |
| 14 |
>> |
| 15 |
> |
| 16 |
> Interesting. I tried it just out of interest and I got two: |
| 17 |
> |
| 18 |
> $ equery b q |
| 19 |
> [ Searching for file(s) q in *... ] |
| 20 |
> app-portage/portage-utils-0.1.29 (/usr/bin/q) |
| 21 |
> sys-libs/ncurses-5.6-r2 (/usr/share/terminfo/q) |
| 22 |
> $ |
| 23 |
> |
| 24 |
> |
| 25 |
|
| 26 |
Hmmm, two apparently different commands with the same name. I thought |
| 27 |
that wasn't supposed to happen? |
| 28 |
|
| 29 |
Dale |
| 30 |
|
| 31 |
:-) :-) |
Archives