Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!europa.eng.gtefsd.com!MathWorks.Com!udel!news.sprintlink.net!news.world.net!news.teleport.com!news.teleport.com!not-for-mail From: mbell@teleport.com (Max Bell) Newsgroups: comp.unix.bsd Subject: Re: Starting .login from a spawned shell ?! Date: 27 Aug 1994 00:04:48 -0700 Organization: Teleport - Portland's Public Access (503) 220-1016 Lines: 17 Message-ID: <33moig$qj4@kelly.teleport.com> References: <Cv4J8s.J5x@ritz.mordor.com> NNTP-Posting-Host: kelly.teleport.com In article <Cv4J8s.J5x@ritz.mordor.com>, Hany Nagib <hany@ritz.mordor.com> wrote: [ . . . ] > When I login for the first time, .login runs automatically (which does >all the prompt and alias settings ...etc.), but after I go in, when I try >to spawn another shell (by typing "tcsh", which is the same shell that I >login to), the .login does NOT run. [ . . . ] A better solution than rerunning your .login file might be to move the commands into your .tcshrc or .cshrc files. Each of these is automatically sourced by each spawned tcsh. The .login file is ideal for those commands you need to use only once per session (like setting the terminal type). -- /\ /\/ Max Bell | I used to think I'd emmigrate to escape / \/ /\ mbell@teleport.com | the tyrants, but now I think I'll stay ~~~~~~~~~ | and make them leave instead.