From: Richard Coleman <coleman@math.gatech.edu>
To: zsh-users@math.gatech.edu
Subject: Re: strange behaviour with .zsh and su
Date: Mon, 14 Apr 1997 14:32:20 -0400 [thread overview]
Message-ID: <199704141832.OAA14699@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "14 Apr 1997 14:20:39 EDT." <5lencd5uvc.fsf@tequila.systemsz.cs.yale.edu>
> Timothy Luoma <luomat@peak.org> 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
next prev parent reply other threads:[~1997-04-14 18:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-14 14:32 Louis-David Mitterrand
1997-04-14 15:06 ` Zefram
1997-04-14 15:47 ` Timothy Luoma
1997-04-14 15:48 ` Louis-David Mitterrand
1997-04-14 16:01 ` Timothy Luoma
1997-04-14 16:14 ` Louis-David Mitterrand
[not found] ` <mito@aparima.com>
1997-04-14 16:54 ` Bart Schaefer
1997-04-14 18:20 ` Stefan Monnier
1997-04-14 18:32 ` Richard Coleman [this message]
1997-04-14 20:27 ` Stefan Monnier
1997-04-14 18:42 ` Tom Howland
1997-04-14 16:02 ` gwing
1997-04-14 17:03 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199704141832.OAA14699@redwood.skiles.gatech.edu \
--to=coleman@math.gatech.edu \
--cc=zsh-users@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).