Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!mcvax!hp4nl!botter!star.cs.vu.nl!maart
From: maart@cs.vu.nl (Maarten Litmaath)
Newsgroups: comp.unix.questions
Subject: Re: Diff between set and setenv
Message-ID: <2363@solo11.cs.vu.nl>
Date: 24 Apr 89 18:27:15 GMT
References: <45000019@uicsrd.csrd.uiuc.edu>
Organization: V.U. Informatica, Amsterdam, the Netherlands
Lines: 29

leein@uicsrd.csrd.uiuc.edu writes:
\In a csh under BSD

\1.  There are things that are to be 'set' and things to be 'setenv'.
\    What is the difference conventionally or logically?

setenv'ed variables will be exported to all programs you execute from your
shell: they are put into the ENVIRONMENT (get it? set-ENV)

\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
.cshrc: variables you want to set in EACH invocation
	- set history = 50

\3. What set and what setenv variables
\   can be transferred from the login shell to the newly created shells?

All setenv'ed variables, no set variable.

\4  Where in the UNIX manual can I find those things in a well organized
\   form?

csh(1), execve(2)
-- 
 "If it isn't aesthetically pleasing, |Maarten Litmaath @ VU Amsterdam:
  it's probably wrong." (jim@bilpin). |maart@cs.vu.nl, mcvax!botter!maart