From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28896 invoked from network); 24 Mar 1999 22:50:11 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 24 Mar 1999 22:50:11 -0000 Received: (qmail 8471 invoked by alias); 24 Mar 1999 22:49:06 -0000 Mailing-List: contact zsh-users-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 2229 Received: (qmail 8464 invoked from network); 24 Mar 1999 22:49:05 -0000 To: zsh-users@sunsite.auc.dk Sender: monnier@tequila.cs.yale.edu From: Stefan Monnier Newsgroups: lists.zsh.users Subject: zsh startup files Date: 24 Mar 1999 17:48:55 -0500 Message-ID: <5l90cmijvs.fsf@tequila.cs.yale.edu> X-Newsreader: Gnus v5.5/Emacs 20.3 Path: tequila.cs.yale.edu NNTP-Posting-Host: tequila.cs.yale.edu X-Trace: 24 Mar 1999 17:48:55 -0500, tequila.cs.yale.edu 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. Stefan "pissed"