From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2449 invoked from network); 2 Apr 1999 17:15:12 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 2 Apr 1999 17:15:12 -0000 Received: (qmail 12665 invoked by alias); 2 Apr 1999 17:14:36 -0000 Mailing-List: contact zsh-users-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 2283 Received: (qmail 12657 invoked from network); 2 Apr 1999 17:14:30 -0000 From: "Bart Schaefer" Message-Id: <990402091308.ZM2312@candle.brasslantern.com> Date: Fri, 2 Apr 1999 09:13:08 -0800 In-Reply-To: <5laewrtbc3.fsf@tequila.cs.yale.edu> Comments: In reply to Stefan Monnier "Re: zsh startup files" (Apr 2, 8:12am) 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> <5laewrtbc3.fsf@tequila.cs.yale.edu> 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 Apr 2, 8:12am, Stefan Monnier wrote: } Subject: Re: zsh startup files } } >>>>> "Bart" == Bart Schaefer writes: } > If you want an example of an even more convoluted initialization system } > that even more people use even more heavily than zsh, I need only point } > you to emacs. } } I beg to disagree. Emacs's initialization is quite a bit simpler Superficially, you're correct. In practice, every autoloaded feature does its own initialization at the time it's loaded, and any serious user employs numerous hook functions and eval-after-load and so on to interleave his own adjustments to that intialization. Even for the simple case, though, there's system init both before and after ~/.emacs ... but you can disable the "after" one, which is what I've been saying should be possible with zsh too. } > Sure. } } These sound like ad-hoc hacks that more or less work in some specific cases. } Very far from the kind of things you'd want to put in /etc/zshrc. I agree about the EXINIT one. Changing the prompt or $LESS is something a sysadmin might do, even if you think he shouldn't. } So you agree in a sense: this fancy ordering is sometimes useful, } but when it is, other alternatives would work as well. What I disagree with about that is the "as well." They'd work *also*, but not *as well*. } I'm all for a /etc/zshenv or maybe even more init files Please, not more. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com