On 1/20/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> On 1/20/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> > Whenever the terminal text color is darker than the background color:
> >
> > fish> set fish_color_comment white
> > fish> echo fish_color_comment
> > white
> > fish> # Comments appear in normal color
> >
> > I'm sure this was intended to ensure that the user can always read the
> > text.  But 'white' actually appears grey in all terminals I have used
> > (Xterm, gnome-terminal, Putty), and text is legible.  I want my
> > completion descriptions and comments grey, on white background.  It is
> > also legible on grey background (I checked).  By contrast, the default
> > comment color, brown (yellow), is not legible on grey.

I think the main point of my post was unclear.  It was that it seems I
cannot make comments appear grey.

> > Perhaps this is a reason to rename 'white' to 'grey'.
>
> I'll check to make sure, but I _think_ fish uses the default ansi
> color names. Terminals implement whatever they like, though. If you
> get grey and want white, it might be worth trying bold + white by
> using
>
> set fish_color_whatever white --bold

But they all seem to want that ANSI color 37 (represented by \033[37m)
appears grey. That seems to me a good reason for calling the color
'grey' rather than 'white'.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users

Reply via email to