On Sat, 19 Jul 2008, Jim Meyering wrote:
Reuben Thomas <[EMAIL PROTECTED]> wrote:
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.
Would you like to prepare a patch that adds to doc/coreutils.texi
the sort of tip you would have liked to see?
I'd rather the maintainers to have dircolors read a configuration file. So
many programs do that, why not dircolors?
--
http://rrt.sc3d.org/ | Il ne vaut pas la peine de peigner l'eau
_______________________________________________
Bug-coreutils mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-coreutils
