From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-2261-mason-zsh=primenet.com.au@sunsite.auc.dk>
Received: (qmail 21736 invoked from network); 31 Mar 1999 07:52:48 -0000
Received: from sunsite.auc.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 31 Mar 1999 07:52:48 -0000
Received: (qmail 19399 invoked by alias); 31 Mar 1999 07:50:35 -0000
Mailing-List: contact zsh-users-help@sunsite.auc.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 2261
Received: (qmail 19387 invoked from network); 31 Mar 1999 07:50:27 -0000
From: "Bart Schaefer" <schaefer@brasslantern.com>
Message-Id: <990330234916.ZM22175@candle.brasslantern.com>
Date: Tue, 30 Mar 1999 23:49:16 -0800
In-Reply-To: <990330231453.ZM22023@candle.brasslantern.com>
Comments: In reply to "Bart Schaefer" <schaefer@brasslantern.com>
        "Re: zsh startup files" (Mar 30, 11:14pm)
References: <9903251002.AA18225@ibmth.df.unipi.it> 
	<199903251055.LAA02436@sally.ifm.uni-kiel.de> 
	<9903251117.AA09841@rouble.olsen.ch> 
	<9903251122.AA14741@ibmth.df.unipi.it> 
	<5l1zidiw46.fsf@tequila.cs.yale.edu> 
	<9903251400.AA54287@ibmth.df.unipi.it> 
	<5lyaklgy2w.fsf@tequila.cs.yale.edu> 
	<990327170423.ZM3271@candle.brasslantern.com> 
	<5logldgt3m.fsf@tequila.cs.yale.edu> 
	<990328175751.ZM8402@candle.brasslantern.com> 
	<19990328231428.A11812@astaroth.nit.gwu.edu> 
	<5l90cmijvs.fsf@tequila.cs.yale.edu> 
	<19990324181547.A4700@astaroth.nit.gwu.edu> 
	<5l7ls6iee4.fsf@tequila.cs.yale.edu> 
	<199903250220.VAA12122@gypsy.cad.gatech.edu> 
	<19990325005332.B5194@astaroth.nit.gwu.edu> 
	<9903250903.AA30753@ibmth.df.unipi.it> 
	<5ln20wgz57.fsf@tequila.cs.yale.edu> 
	<002501be79f0$86c54620$21c9ca95@mowp.siemens.ru> 
	<990330231453.ZM22023@candle.brasslantern.com>
X-Mailer: Z-Mail (4.0b.820 20aug96)
To: zsh-users@sunsite.auc.dk
Subject: Re: zsh startup files
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Mar 30, 11:14pm, Bart Schaefer wrote:
} Subject: Re: zsh startup files
}
} [...] Boy, would it have been simpler for all concerned if csh had
} always read an /etc/csh.login back then. (And guess what tcsh does
} now? And guess in what order WRT the user's .cshrc?)

Before someone else corrects me ... I just noticed that tcsh reads both
of the /etc/csh* files first.  My recollection had been that it was
interleaved like zsh, and that this is where the idea for zsh's system
came from ... but if it ever was, it's not any more for tcsh.

That doesn't change my opinion, but I'll grant that it's a data point
in favor of untangling them.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com