Path: utzoo!attcan!uunet!husc6!uwvax!oddjob!ncar!ames!fxgrp!ljz
From: ljz@fxgrp.UUCP (Lloyd Zusman)
Newsgroups: comp.unix.questions
Subject: A csh question ...
Summary: Why .login *after* .cshrc?
Keywords: csh question .login .cshrc
Message-ID: <636@fxgrp.UUCP>
Date: 20 May 88 21:18:29 GMT
Reply-To: ljz%fx.com@ames.arc.nasa.gov (Lloyd Zusman)
Organization: Master Byte Software, Los Gatos, California
Lines: 26

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.

I end up doing things like the following hack to get around this:

    # This resides at the top of a hypothetical .cshrc file ...

    if (! ${?FIRST_TIME_THROUGH}) then
    	setenv FIRST_TIME_THROUGH
    	# do all sorts of startup stuff that I would prefer to put
    	# into .login if it were only sourced before .cshrc
    endif

    ...

Are there any csh's out there that do this differently, perhaps if some
command-line flag is set?

--
  Lloyd Zusman                          UUCP:   ...!ames!fxgrp!ljz
  Master Byte Software              Internet:   ljz%fx.com@ames.arc.nasa.gov
  Los Gatos, California               or try:   fxgrp!ljz@ames.arc.nasa.gov
  "We take things well in hand."