Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83 (MC840302); site diku.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!mcvax!diku!kimcm
From: kimcm@diku.UUCP (Kim Christian Madsen)
Newsgroups: net.bugs.4bsd
Subject: Re: vi bug, or how to set up .cshrc
Message-ID: <1129@diku.UUCP>
Date: Sun, 11-Aug-85 02:12:15 EDT
Article-I.D.: diku.1129
Posted: Sun Aug 11 02:12:15 1985
Date-Received: Mon, 12-Aug-85 22:49:28 EDT
References: <144@peregrine.UUCP> <190@ittral.UUCP> <171@telesoft.UUCP> <2585@sun.uucp>
Reply-To: kimcm@diku.UUCP (Kim Christian Madsen)
Organization: DIKU, U of Copenhagen, DK
Lines: 21

In article <2585@sun.uucp> gnu@sun.uucp (John Gilmore) writes:
>KEITH F. PILOTTI of TeleSoft said:
>>     Under 4.2BSD, the best solution seems to be the following:
>> 
>>         set path = ( . ~ ~/bin ~/frammis /usr/ucb /usr/bin /bin )
>>         if ( ! $?prompt ) exit
>>         ...
>>         
>
>Actually, the "set path" is not needed.  Path is put into the
>environment variable PATH, which persists across all processes you
>create.  Set it in your .login .

Well, I agree that it should be superflous to set the path other places
than in your login. But if you are about to pipe data through a remote shell
(rsh) the path variable will be needed in your .cshrc or you will have to
give full pathname on the remote system.

					Regards
					Kim Chr. Madsen
				a.k.a.	kimcm@diku.uucp