From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7290 invoked from network); 20 Apr 1999 16:34:23 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 20 Apr 1999 16:34:23 -0000 Received: (qmail 24121 invoked by alias); 20 Apr 1999 16:34:17 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6064 Received: (qmail 24112 invoked from network); 20 Apr 1999 16:34:15 -0000 From: "Bart Schaefer" Message-Id: <990420093329.ZM3000@candle.brasslantern.com> Date: Tue, 20 Apr 1999 09:33:29 -0700 In-Reply-To: <9904160751.AA36373@ibmth.df.unipi.it> Comments: In reply to Peter Stephenson "Startup files" (Apr 16, 9:51am) References: <9904160751.AA36373@ibmth.df.unipi.it> X-Mailer: Z-Mail (4.0b.820 20aug96) To: zsh-workers@sunsite.auc.dk (Zsh hackers list) Subject: Re: Startup files MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Apr 16, 9:51am, Peter Stephenson wrote: } Subject: Startup files } } It's probably not too late to alter GLOBAL_RCS_FIRST into something else Agreed. (In fact, sort of by definition there's nothing new in 3.1.x that we can't alter, but in practice I suppose anything pre-3.1.4 is pretty much locked in.) } What would be the preferred strategy? Test NO_RCS before every script } apart from /etc/zshenv, and skip them if it's set? Does this meet } everybody's requirements? Semantically, that would do it for me. However, I wonder if it's going to cause any problems ... I don't imagine anyone sets NO_RCS just to turn off the logout files, but it's possible. Maybe the right thing is a new flag that could be set in ~/.zshenv to disable only the (remaining) global files. The sysadmin still gets his shot in /etc/zshenv, and thereafter it's simple for the user to get back control and keep it. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com