Hi,

I just wanted to give an update on compiling fish on an older system 
(Slackware 8.0, from 2001). Following Egon's tip, I upgraded gcc from 
gcc-2.95.3 to gcc-3.2.3 and as a result fish now happily compiles (with 
glibc-2.2.3 and doxygen-1.2.18).

Unfortunately, though, whenever I try to start fish I get the following 
error message:


[EMAIL PROTECTED] fish
fish: Co
StandardWelcome to fish, the friendly interactive shell
Type help for instructions on how to use fish
set_color: Expected an argument
[EMAIL PROTECTED] set_color - Set the terminal color       \section 
set_color-synopsis  set_color [-v --version] [-h       --help] [-b 
--background COLOR] [COLOR]> @       \section set_color-description        
Change the foreground and/or background color of the       terminal. 
COLOR is one of black, red, green, brown,>        yellow, blue, magenta, 
purple, cyan, white and normal.@        -c, --print-colors Prints a list 
of all valid color names       -b, --background Set the background 
color> @       -o, --bold Set bold or extra bright mode        -h, 
--help Display help message and exit>        -v, --version Display 
version and exit@        Calling set_color normal will set the terminal 
color to       whatever is the default color of the terminal.>        
Some terminals use the --bold escape sequence to switch to@       a 
brighter color set. On such terminals, set_color white        will 
result in a grey font color, while set_color --bold       white will 
result in a white font color.> ~@ > 


This happens consistently on the console, in xterm, and in rxvt. In 
fact, this seems to be basically the same problem that Stefan Nicolin 
described using fish on Mac OS X Tiger back in Dec. (but to which no one 
replied):

http://sourceforge.net/mailarchive/forum.php?thread_id=9297954&forum_id=45104

I should add that set_color alone can change the color on the console on 
my system but it seems to have no effect in xterm or rxvt (but it 
doesn't give an error when used alone in either case).

Does anyone have an idea what is causing the error above? It looks like 
a kind of parsing error.

As nice as fish seems, it does appear to tacitly assume a rather recent
system to work as intended, which is OK, but it would be nice to try to
make these assumptions as explicit as possible.

Christopher


-------------------------------------------------------
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&kid=103432&bid=230486&dat=121642
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users

Reply via email to