Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!husc6!contact!ileaf!io!pme
From: pme@io.UUCP (Paul English x3168)
Newsgroups: comp.unix.questions
Subject: Re: Diff between set and setenv
Message-ID: <1040@io.UUCP>
Date: 25 Apr 89 14:21:05 GMT
References: <45000019@uicsrd.csrd.uiuc.edu> <2363@solo11.cs.vu.nl>
Reply-To: pme@ileaf.com (Paul English)
Organization: Interleaf, Cambridge, MA
Lines: 25

In article <2363@solo11.cs.vu.nl> maart@cs.vu.nl (Maarten Litmaath) writes:
>leein@uicsrd.csrd.uiuc.edu writes:
>\2. What variables should go to .login only, and what variables should 
>\   go to .cshrc only?
>
>.login: variables you only want to set ONCE (typically environment variables)
>	- setenv PATH $HOME/bin:/bin:/usr/bin:/usr/ucb:/usr/local/bin

Some users find it preferable to set the path explicitly in their
.cshrc so commands invoked remotely with rsh will use the correct
path.

Also, `su username' will begin a new shell as `username', reading only
the .cshrc (for csh). However, `su - username' will also read the
.login file.

Also (I know most people already know this), make sure any aliases you
want are set in your .cshrc instead of your .login. The way many
people setup their window system environments, the .login file is not
read at the start of the shell for each new window.
-- 
Paul English
  Interleaf: pme@ileaf.com, ...!{sun!sunne,mit-eddie}!ileaf!pme
  UMass/Boston: pme@umb.edu, ...!harvard!umb!pme
(umb has better email service)