Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: zsh startup files

On Wed, Mar 24, 1999 at 05:48:55PM -0500, Stefan Monnier wrote:
> Am I the only one that keeps getting annoyed by the sequence in which startup
> files are read ?  It seems to be especially designed to make it easy for the
> sysadmin to come up with a setup that is painful to override by users.
> As a user and a syadmin who cares about users who like to override the
> sysadmin's decisions, I think it should be changed.  Instead of something like
>     /etc/zshenv ~/.zshenv /etc/zprofile ~/.zprofile /etc/zshrc ~/.zshrc ...
> I suggest
>     /etc/zshenv /etc/zprofile /etc/zshrc /etc/zlogin ~/.zshenv ~/.zprofile ...
> This way the sysadmin can put in /etc/zprofile commands that should only be
> executed at login time without having to worry about interference with the
> user's ~/.zshenv settings.
> And this way, when the sysadmin (or RedHat package maintainers) decide to put
> bogus PATH and umask settings in /etc/zshrc it won't override my ~/.zprofile
> choices.

	i think the idea is that the same sorts of commands will go in the
equivalent system-wide and user-specific files, so that by sourcing the
user files right after the relevant system files, the user can always override
the system options.  in other words, if your sysadmin is setting PATH and umask 
in /etc/zshrc, try setting it to your value in your own .zshrc instead of your 

	-- sweth.

Sweth Chandramouli
IS Coordinator, The George Washington University
<sweth@xxxxxxx> / (202) 994 - 8521 (V) / (202) 994 - 0458 (F)
<a href="http://astaroth.nit.gwu.edu/~sweth/disc.html";>*</a>

Messages sorted by: Reverse Date, Date, Thread, Author