I would still tend to agree with your earlier analysis: the fact that it doesn't do what it's supposed to do is this bug, and the fact that it would be nice to be able to turn it off is a separate bug.
What would be a suitable mechanism for turning it off if desired? I don't particularly like the idea of using a signal file in the user's home directory. Since this is in .bashrc, the user might want to set an environment variable in their .bash_profile to turn off color options; would that be a suitable solution? - if (tput setaf 1) >&/dev/null + if ! test "$BASH_NO_COLOR" && (tput setaf 1) >&/dev/null I would also like to put that dreadful "alias ls='ls --color=auto'" inside this conditional. There may be other parts of the default .bashrc which ought to be similarly refactored into this conditional, too. -- Bash prompt string looks for xterm-color, gnome terminal identifies as xterm https://bugs.launchpad.net/bugs/103929 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
