Philip Webb wrote: > 190817 Dale wrote: >> It says this in the link provided : "Note that this behavior is now >> on by default, but it can be disabled." >> I've looked and I can not find where to disable that feature. > Sorry, I can't help there : keep looking (smile). > >> Can you narrow down CLI for me? > 'Command-line interface' : a good old terminal ... > > I supplement that with some .bashrc aliases + functions. > I also use 'cdargs' -- yes, you can 'eix' that one -- , > which makes it easier to jump around the file system.
Ah, OK. I thought it was some nifty file manager that I hadn't heard of. Explains why I couldn't find it, in the long list of cli hits. A LOT of packages have the name "client" in it. Searching for cli with those names makes it a long list. ;-) >> I already switched to Krusader for root access >> so it's not like I'm not totally against using something else. > Krusader is a bit powerful for ordinary little move/copy/read's, > but there's no reason you couldn't use it like that, if you need to. > I use it mostly when I'm doing upgrades. I edit keywords, USE flags and such with it. I don't use it often but it runs as root without me having to keep up with patches and all that stuff. If the upstream devs want to disable features that are needed, I use something else. I'm still looking for a way to disable that thing, it has to be called something I don't recognize or something. I just don't see it. I have looked in places that it shouldn't even be to be honest. :/ Dale :-) :-)
