From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14603 invoked from network); 14 Apr 1997 18:41:16 -0000 Received: from euclid.skiles.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 14 Apr 1997 18:41:16 -0000 Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id OAA08968; Mon, 14 Apr 1997 14:35:36 -0400 (EDT) Resent-Date: Mon, 14 Apr 1997 14:32:55 -0400 (EDT) Message-Id: <199704141832.OAA14699@redwood.skiles.gatech.edu> To: zsh-users@math.gatech.edu Subject: Re: strange behaviour with .zsh and su In-reply-to: Your message of "14 Apr 1997 14:20:39 EDT." <5lencd5uvc.fsf@tequila.systemsz.cs.yale.edu> Date: Mon, 14 Apr 1997 14:32:20 -0400 From: Richard Coleman Resent-Message-ID: <"_rD5J3.0.j92.MXdKp"@euclid> Resent-From: zsh-users@math.gatech.edu X-Mailing-List: archive/latest/810 X-Loop: zsh-users@math.gatech.edu X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu > Timothy Luoma writes: > > The zshenv file includes a loop which sources any file found in > > $HOME/Unix/zsh/source, so I have several files in there: > > I don't know why shell writers insist on using several init files. > The .login/.zshprofile/.zshlogin file isn't sourced every time you'd need it > (typically, it's not sourced from an XDM login), so you need to move stuff from > there into zshenv. > > On another hand, a variable indicating whether the shell is a login shell is > necessary (and sadly missing from tcsh). I think zsh's method for startup files is the most logical of all the common shells. .zshenv -- invoked on every startup .zshrc -- invoked for interactive shells .zlogin -- invoked for login shells .zlogout -- invoked on logout This give you complete flexibility. I wouldn't want all that stuff in a single file. Of course you need to might sure things are in the right file, but you only need to do that once. rc