> On 08/17/2010 10:18 PM, Beni Cherniavsky-Paskin wrote: >> Thanks, updated the wiki with your solution. >> I had a much more involved scheme somewhere, allowing switching both ways. >> Will try to find and post it too next week when I get home. >> >> Which reminds me of a question: should $SHELL be set to /usr/bin/fish or >> not? >> I'm not clear on what it affects, and whether it's safe to use a >> bourne-incompatible $SHELL. >> Can anyone shed light on this?
It works fine. Any program that uses $SHELL to execute scripts assuming that $SHELL is a bourne or posix shell is, simply, broken (and I've never run into one yet -- the legacy of csh/tcsh probably trained people not to). $SHELL is only to be used to create an interactive shell for the user. On 08/18/10 06:21, Tom W. Most wrote: > The only major issue --- and it's a fish issue, not a Bourne shell > incompatibility --- is that fish hangs when used as the login shell at a > text console. It works fine for me. I login to text console and then `startx` every time I boot, and I sometimes go to the text consoles and log in later too. Actually, my $SHELL is a shell-script I wrote that does some initializations and then invokes fish: cat $SHELL #!/bin/sh #...do some silly stuff... exec fish "$@" ...which, surprisingly, works just fine. (At least in my setup.) -Isaac ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
