From: Stefan Monnier <monnier+lists/zsh/users/news/@tequila.cs.yale.edu>
To: zsh-users@sunsite.auc.dk
Subject: Re: zsh startup files
Date: 02 Apr 1999 08:12:59 -0500 [thread overview]
Message-ID: <5laewrtbc3.fsf@tequila.cs.yale.edu> (raw)
In-Reply-To: <990330231453.ZM22023@candle.brasslantern.com>
>>>>> "Bart" == Bart Schaefer <schaefer@brasslantern.com> writes:
> If you want an example of an even more convoluted initialization system
> that even more people use even more heavily than zsh, I need only point
> you to emacs.
I beg to disagree. Emacs's initialization is quite a bit simpler:
site-lisp/site-start.el ~/.emacs site-lisp/default.el
three simple steps where the last one can be disabled in either
of the first two.
> Sure. One, I set up the $LESS environment in zshrc, with z$[LINES-2] (set
> scroll height to two less than $LINES). Two, I used to have a multi-line
> $PS1, which I also set in zshrc, that depended on $COLUMNS, and that was
> not used at all when the terminal was "emacs" or "dumb". Three, I played
> for a while with different .exrc files for fast and slow connections; I
> set up $EXINIT based on the terminal type (yes, that's what $BAUD is for,
> but it was wrong for other reasons, and passing extra data through rlogin
> by stuffing it into $TERM and then parsing it out again is a time-honored
> hack). All these go in zshrc because they're useless to non-interactive
> shells, but sometimes necessary even in non-login ones (think "su" if
> nothing else).
These sound like ad-hoc hacks that more or less work in some specific cases.
Very far from the kind of things you'd want to put in /etc/zshrc.
> The interleaving of init files let me get away with that last one, because
> I could demangle $TERM in my .zshenv before /etc/zprofile ran. A system
The $TERM mangling is an interesting case. I'd tend to say that if
a /etc/zprofile or /etc/zshenv doesn't work with such a thing, it's broken.
It might work suboptimally, tho.
> Of course at this point (cf. the "exec" trick) I'm more likely to want to
> bypass the system files entirely, but that wasn't always the case, and
> sometimes isn't worth bothering with (I was just at a consulting job
> where the /etc/z* files did extensive environment setup for a collection
> of homegrown custom build tools; it would have been silly to try to redo
> it or reorder it).
So you agree in a sense: this fancy ordering is sometimes useful,
but when it is, other alternatives would work as well.
> Back when I was at OGI, the login banner had to announce that any user
> whose .login was found _not_ to contain a certain set of commands, would
> lose their access to the system.
I'm all for a /etc/zshenv or maybe even more init files (as a sysadmin
I really like to setup some envvars in there), but that has no relation to
whether these should be sourced in such an interleaved manner.
Stefan
next prev parent reply other threads:[~1999-04-02 13:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-24 22:48 Stefan Monnier
1999-03-24 23:15 ` Sweth Chandramouli
1999-03-25 0:47 ` Stefan Monnier
1999-03-25 5:53 ` Sweth Chandramouli
1999-03-25 11:17 ` Doug Morris
1999-03-25 2:20 ` Jason Price
1999-03-25 9:03 ` Peter Stephenson
[not found] ` <9903251002.AA18225@ibmth.df.unipi.it>
1999-03-25 10:55 ` Wolfgang Hukriede
1999-03-25 11:22 ` Peter Stephenson
1999-03-25 12:36 ` Stefan Monnier
1999-03-25 14:00 ` Peter Stephenson
1999-03-25 19:37 ` Stefan Monnier
1999-03-28 1:04 ` Bart Schaefer
1999-03-28 22:14 ` Stefan Monnier
1999-03-29 1:57 ` Bart Schaefer
1999-03-29 4:14 ` Sweth Chandramouli
1999-03-29 14:15 ` Stefan Monnier
1999-03-29 14:29 ` Andrej Borsenkow
1999-03-31 7:14 ` Bart Schaefer
1999-03-31 7:49 ` Bart Schaefer
1999-04-02 13:12 ` Stefan Monnier [this message]
1999-04-02 17:13 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2006-03-14 17:38 zzapper
2006-03-14 19:50 ` Wayne Davison
2006-03-15 2:43 ` Bart Schaefer
2006-03-15 18:22 ` Phil Pennock
2006-03-16 19:29 ` Dominic Mitchell
1996-10-19 23:04 Zsh " Nate Johnston
1996-10-20 11:09 ` Zefram
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=5laewrtbc3.fsf@tequila.cs.yale.edu \
--to=monnier+lists/zsh/users/news/@tequila.cs.yale.edu \
--cc=zsh-users@sunsite.auc.dk \
/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).