Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site telesoft.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!sdcrdcf!sdcsvax!telesoft!pilotti From: pilotti@telesoft.UUCP (Keith Pilotti @shine) Newsgroups: net.bugs.4bsd Subject: Re: vi bug, or how to set up .cshrc Message-ID: <173@telesoft.UUCP> Date: Sun, 18-Aug-85 06:27:15 EDT Article-I.D.: telesoft.173 Posted: Sun Aug 18 06:27:15 1985 Date-Received: Sun, 25-Aug-85 04:42:38 EDT References: <144@peregrine.UUCP> <190@ittral.UUCP> <171@telesoft.UUCP> Organization: TeleSoft, SanDiego CA Lines: 36 Summary: <2585@sun.uucp> Sender: Reply-To: pilotti@telesoft.UUCP (Keith Pilotti @shine) Followup-To: Distribution: Organization: TeleSoft, San Diego, CA Keywords: In article <2585@sun.uucp> gnu@sun.uucp (John Gilmore) writes: >KEITH F. PILOTTI of TeleSoft said: >> >> 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 . This is true, except for remote commands. 4.2BSD `rsh' does not propagate PATH across to the remote machine. The remote process gets a system default PATH modified by ".cshrc". >Also note that it's often a bad idea to put "." ahead of the standard >directories in your path. This leaves you open to trojan horses >that will run when you type "cat" or "ls" as you look around. I like suprises, and personally consider finding trojan horses a feature :-), however I agree that the *Super-User*'s path should NOT contain "." ! The above ".cshrc" example, without the ".", installed in /.cshrc is a good way to guarantee this. /+\ Keith P ________________________________________________________ ...{decvax,ucbvax}!sdcsvax!telesoft!pilotti