Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!cs.utexas.edu!uunet!pdn!palan!ckctpa!crash
From: crash@ckctpa.UUCP (Frank J. Edwards)
Newsgroups: comp.unix.amiga
Subject: Re: SVR4 /bin/sh BUG
Message-ID: <1991Jun19.163713.5797@ckctpa.UUCP>
Date: 19 Jun 91 16:37:13 GMT
References: <1991Jun15.014909.1562@menudo.uh.edu> <2671@amix.commodore.com>
Organization: Edwards & Edwards Consulting
Lines: 33

In article <2671@amix.commodore.com> ag@amix.commodore.com (Keith Gabryelski) writes:
>FYI, csh has the a shell variable named `shell' that keep the name of
>shell to interpret non-system executable commands (ie, shell scripts).
>If you typically use csh for interactive use and another (Bourne?) for
>shell scripts use:
>
>	set shell=/bin/sh

Yes, but some csh implementations also require

	% alias shell=/bin/sh

which is prepended to any command line which attempts to exec() a file
which fails; the alias is prepended and the exec() is tried again.

Of course, this breaks other things in the shell (sigh).  Oh well, good
riddance to csh!

>Pax, Keith
>-- 
>Keith Gabryelski                                 Advanced Products Group
>ag@amix.commodore.com                                 ...!cbmvax!amix!ag

I did notice, though, that you Amix folks have fixed the SVR4 csh bug
concerning changing directory two levels into a symbolic link, and
then backing out again with "cd .."  My question is, "why in the world
did csh even care?!"  (Er, rhetorical question.  One does not ask _why_
the C shell does what it does...)
-- 
Frank J. Edwards		|  "I did make up my own mind -- there
2677 Arjay Court		|   simply WASN'T ANY OTHER choice!"
Palm Harbor, FL  34684-4504	|		-- Me
Phone (813) 786-3675 (voice)	|    Only Amiga Makes It Possible...