On Friday 10 Jun 2011 19:18:06 Paul Hartman wrote: > On Fri, Jun 10, 2011 at 12:41 PM, Dale <rdalek1...@gmail.com> wrote: > > Nikos Chantziaras wrote: > >> On 06/09/2011 09:52 PM, Bill Longman wrote: > >>> On 06/09/2011 11:18 AM, Alan McKinnon wrote: > >>>> eselect OTOH, is something I always have to run bit by bit to recall > >>>> the invocation. That's just way too much effort for this here old > >>>> git.... > >>> > >>> Wasn't on this list that I saw the correct procedure for eselect? > >>> > >>> eselect > >>> eselect kernel > >>> eselect kernel list > >>> eselect kernel set 6 > >>> > >>> <sigh> It's so true.... > >> > >> Never happened to me. I simply enter "eselect" and then press TAB twice > >> and get a list of every module :-P > > > > Huh? > > > > root@fireball / # eselect < hit tab twice here > > > bin/ .config/ dev/ home/ lib/ lib64/ mnt/ opt/ > > root/ sys/ usr/ > > boot/ data/ etc/ kde lib32/ media/ old-etc/ proc/ > > sbin/ tmp/ var/ > > root@fireball / # eselect > > See Pandu's latest message in this thread. Once you enable it like he > showed, it'll work like this: > > # eselect <pressed tab twice here> > bashcomp boost ctags fontconfig java-vm > locale news pager python usage > visual > binutils --brief editor help kernel > mesa --no-colour pinentry rc > version wxwidgets > blas cblas env java-nsplugin lapack > modules opengl profile ruby vi > xvmc
Not here: # eselect bashcomp list Available completions: [1] gdbus [2] gsettings # eselect bashcomp enable eselect !!! Error: /usr/share/bash-completion/eselect doesn't exist -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
