vi bug, or how to set up .cshrc

[Keith Pilotti @shine]

<2585 at sun.uucp>
Sender: 
Reply-To: pilotti at telesoft.UUCP (Keith Pilotti @shine)
Followup-To: 
Distribution: 
Organization: TeleSoft, San Diego, CA
Keywords: 

In article <2585 at sun.uucp> gnu at 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
    ________________________________________________________

          <pilotti at telesoft.UUCP> <pilotti at UCSD.ARPA>
          ...{decvax,ucbvax}!sdcsvax!telesoft!pilotti