The current version of skel/.bashrc in Intrepid is nonsense as regards this issue. We still have code that checks $TERM against "xterm-color", and enables the color prompt if so. This fails for most terminals, of course. Then we have a variable, force_color_prompt, which we may set to yes to *enable* a more sensible detection of a color-capable terminal, which, if we pass, sets up a color prompt.
This is nonsense because not only do we turn on the color prompt rather inconsistently for xterm-color, which is the old behavior that was deemed to be Wrong (and confusing and ineffective), but also the variable force_color_prompt does not in fact *force* anything. The check against xterm-color should be removed because it is no longer necessary. The force_color_prompt variable should be renamed enable_color_prompt, allow_color_prompt, or maybe conditional_color_prompt. Finally, the obnoxiously moralizing comment that color prompts are for lusers is entirely inappropriate and should be removed.
The current version of skel/.bashrc in Intrepid is nonsense as regards this issue. We still have code that checks $TERM against "xterm-color", and enables the color prompt if so. This fails for most terminals, of course. Then we have a variable, force_color_prompt, which we may set to yes to *enable* a more sensible detection of a color-capable terminal, which, if we pass, sets up a color prompt.
This is nonsense because not only do we turn on the color prompt rather inconsistently for xterm-color, which is the old behavior that was deemed to be Wrong (and confusing and ineffective), but also the variable force_color_prompt does not in fact *force* anything. The check against xterm-color should be removed because it is no longer necessary. The force_color_prompt variable should be renamed enable_ color_prompt, allow_color_prompt, or maybe conditional_ color_prompt. Finally, the obnoxiously moralizing comment that color prompts are for lusers is entirely inappropriate and should be removed.