Path: utzoo!dciem!nrcaer!scs!spl1!laidbak!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!necntc!ima!cfisun!lakart!dg
From: dg@lakart.UUCP (David Goodenough)
Newsgroups: comp.unix.questions
Subject: Re: A csh question ...
Message-ID: <142@lakart.UUCP>
Date: 31 May 88 13:28:27 GMT
Article-I.D.: lakart.142
References: <3872@fluke.COM>
Organization: Lake - The systems people
Lines: 29

>In article <636@fxgrp.UUCP> ljz%fx.com@ames.arc.nasa.gov (Lloyd Zusman) writes:
>}A question concerning csh:
>}Can anyone explain why .login gets sourced *after* .cshrc?  I am constantly
>}running into situations where I'd like .login to get sourced first, and I
>}cannot see any good reasons for why it should get sourced after .cshrc.
>
And in article <3872@fluke.COM>, strong@tc.fluke.COM (Norm Strong) replies:
> Why not put the contents of your .login file in your .cshrc file?

The reason that I believe it is done is to allow such things as

unset ignoreeof		# in ~/.cshrc

and then

set ignoreeof		# in ~/.login

Now this means that in all your c-shells except your login shell will respect
a ^D to exit, but you explicitly have to say "logout" or "exit" to your
login shell to get it to go away i.e. hammering ^D will return you to your
login shell but will stop there. The basic notion is that you set your
environment with .cshrc, and thene make any login shell changes (and of course
login only commands) in your .login. Now if anyone knows different they will
doubtless speak up :-) :-)
-- 
	dg@lakart.UUCP - David Goodenough		+---+
							| +-+-+
	....... !harvard!adelie!cfisun!lakart!dg	+-+-+ |
						  	  +---+