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!sundog.tiac.net!usenet.elf.com!rpi!ghost.dsi.unimi.it!univ-lyon1.fr!ensta!itesec!keltia.frmug.fr.net!not-for-mail From: roberto@keltia.frmug.fr.net (Ollivier Robert) Newsgroups: comp.os.386bsd.questions Subject: Re: Starting .login from a spawned shell ?! Date: 26 Aug 1994 21:57:25 +0200 Organization: A Happy FreeBSD 1.1.5 Usenet Site Lines: 24 Message-ID: <33lhfj$1kt@keltia.frmug.fr.net> References: <Cv4J5E.J2H@ritz.mordor.com> Reply-To: roberto@hsc.fr.net (Ollivier Robert) NNTP-Posting-Host: keltia.frmug.fr.net Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit In article <Cv4J5E.J2H@ritz.mordor.com>, Hany Nagib <hany@ritz.mordor.com> wrote: > Hi .. > to spawn another shell (by typing "tcsh", which is the same shell that I > login to), the .login does NOT run. I get the system prompt, and no That's expected. .login is supossed to be run _only_ at login hence the name :-) > defined aliases at all in my new spawned shell. Yet when I exit that and > go back to my original login shell, everything is back to normal. > So .. my question is .. how do I make the .login run automatically every > time I spawn a new shell ? Use the .tcshrc file for aliases, variables (set foo=). It is run each time you spawn a shell. .login is for environment variables (setenv FOO bar), stty settings. ``man tcsh'' is generally rewarding. -- Ollivier ROBERT roberto@hsc.fr.net Hervé Schauer Consultants Ollivier.Robert@keltia.frmug.fr.net PERL / MIME / PGP / 4.4BSD FreeBSD keltia 1.1.5(RELEASE) KELTIA#0 i386