Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 +MULTI+2.11; site stc.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!harvard!seismo!mcvax!ukc!stc!andrew
From: andrew@stc.UUCP (Andrew Macpherson)
Newsgroups: net.bugs.4bsd
Subject: Re: vi bug(feature?) (really csh)
Message-ID: <570@stc-b.stc.UUCP>
Date: Thu, 5-Sep-85 13:48:21 EDT
Article-I.D.: stc-b.570
Posted: Thu Sep  5 13:48:21 1985
Date-Received: Sat, 7-Sep-85 07:02:26 EDT
References: <144@peregrine.UUCP> <190@ittral.UUCP> <155@graffiti.UUCP>
Reply-To: Andrew Macpherson <andrew@stc.UUCP>
Distribution: net
Organization: STC Telecoms, London N11 1HB.
Lines: 19
Xpath: stc stc-b stc-a

In article <155@graffiti.UUCP> peter@graffiti.UUCP (Peter da Silva) writes:
>Oh yeh, my main gripe with CSH: It expands *history* in non-interactive shells,
>which makes it a pain to do a uucp mail from vi, which also expands history.
>My solution? At the end of my .cshrc I add the line: "setenv SHELL /bin/sh".

That's rather extreme: how about

if ( ! $?prompt ) then
	set histchars=''
	exit
endif
interactive csh bits...

That way you can still get your real SHELL from more and simmilar...

-- 
Regards,
	Andrew Macpherson.	<andrew@stc.UUCP>
	{creed, datlog, idec, iclbra, iclkid, root44, stl, ukc}!stc!andrew