From: Stefan Monnier <monnier+/news/lists/zsh/users@TEQUILA.SYSTEMSZ.CS.YALE.EDU>
To: zsh-users@math.gatech.edu
Subject: Re: strange behaviour with .zsh and su
Date: 14 Apr 1997 16:27:43 -0400 [thread overview]
Message-ID: <5lbu7h5ozk.fsf@tequila.systemsz.cs.yale.edu> (raw)
In-Reply-To: <199704141832.OAA14699@redwood.skiles.gatech.edu>
Richard Coleman <coleman@math.gatech.edu> writes:
> 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
If it is the most logical for you, it's fine. But if it isn't, it does all
those lookups for no reason. Actually, I don't care so much, I don't have to
use them, right ? (my .zprofile and .zlogin are always empty since I mostly
login via XDM anyway)
The problem is more with /etc/zprofile and /etc/zlogin since you have to be
careful with what you put in there: it might very well break (be broken by)
..zshenv (and even .zprofile and .zshrc for the /etc/zlogin).
I'd be perfectly happy with
/etc/zshenv, /etc/zshrc, ~/.zshenv, ~/.zshrc
This way there is no weird interaction between user's and system's files.
Anyway, this is all hot-air because it's not going to change any time soon,
Stefan
next prev parent reply other threads:[~1997-04-14 20:32 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
1997-04-14 20:27 ` Stefan Monnier [this message]
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=5lbu7h5ozk.fsf@tequila.systemsz.cs.yale.edu \
--to=monnier+/news/lists/zsh/users@tequila.systemsz.cs.yale.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).