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