On Sat, 19 Jul 2008, Jim Meyering wrote:
Reuben Thomas <[EMAIL PROTECTED]> wrote:
It would both be logical, and help with testing (where one wouldn't
have to change one's login script) if dircolors tried to load
~/.dircolors if no database is given and the file exists.
Or just put this in your start-up script:
d=.dircolors
test -r $d && eval "$(dircolors $d)"
That's fine, but, as always, good default behaviour is worth a hundred times
as much as configuration: it doesn't need a user to work it out, read your
mailing list message, or anything else. On the other hand, you could improve
the differential by putting the above tip in the dircolors documentation.
I have solved the problem for myself by simply accepting dircolors's default
settings, which have now pretty much caught up with everything I ever
configured, and also avoids confusion when I log in to systems on which my
customisation is not installed.
--
http://rrt.sc3d.org/ | robber, n. a candid man of affairs (Bierce)
_______________________________________________
Bug-coreutils mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-coreutils
