Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zsh startup files
- X-seq: zsh-users 2238
- From: Stefan Monnier <monnier+lists/zsh/users/news/@tequila.cs.yale.edu>
- To: zsh-users@xxxxxxxxxxxxxx
- Subject: Re: zsh startup files
- Date: 25 Mar 1999 07:36:57 -0500
- Mailing-list: contact zsh-users-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <199903251055.LAA02436@xxxxxxxxxxxxxxxxxxxxx> <9903251122.AA14741@xxxxxxxxxxxxxxxxx>
- Sender: monnier@xxxxxxxxxxxxxxxxxxx
>>>>> "Peter" == Peter Stephenson <pws@xxxxxxxxxxxxxxxxx> writes:
> This makes things rather complicated; there's no fundamental difficulty,
> but I'd prefer to keep it clean. The idea is not that you're at war with
> the sysadmin, who's supposed to make it easy for users to set their own
> preferences. But if this is popular enough...
No. /etc/zshrc is too often misused (and the "supposed" is of paramount
importance in the above sentence).
Actually, now that I think about it, why do we even need all those /etc/z*
files ? It seems that all except for either /etc/zprofile or /etc/zshenv
should be kept empty in all but really unusual circumstances (in which case
you can still use zshenv for the same purpose).
I guess I could live with just NO_GLOBAL_RCS that I would
set in my .zshenv although it won't do me any good as a sysadmin.
Now, how can I simulate NO_GLOBAL_RCS (I don't want to wait for my
sysadmins to install a newer zsh version) ?
How can I determine from .zshenv whether or not .zshrc (and .zprofile)
would be sourced if NO_RCS wasn't set ?
Stefan
Messages sorted by:
Reverse Date,
Date,
Thread,
Author