From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21464 invoked from network); 20 Jan 2009 19:49:11 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 20 Jan 2009 19:49:11 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 52061 invoked from network); 20 Jan 2009 19:49:06 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 20 Jan 2009 19:49:06 -0000 Received: (qmail 12678 invoked by alias); 20 Jan 2009 19:49:01 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 26382 Received: (qmail 12663 invoked from network); 20 Jan 2009 19:49:01 -0000 Received: from bifrost.dotsrc.org (130.225.254.106) by sunsite.dk with SMTP; 20 Jan 2009 19:49:01 -0000 Received: from mtaout01-winn.ispmail.ntl.com (mtaout01-winn.ispmail.ntl.com [81.103.221.47]) by bifrost.dotsrc.org (Postfix) with ESMTP id 004ED80271F0 for ; Tue, 20 Jan 2009 20:48:53 +0100 (CET) Received: from aamtaout03-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout01-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20090120194853.QMHA2989.mtaout01-winn.ispmail.ntl.com@aamtaout03-winn.ispmail.ntl.com> for ; Tue, 20 Jan 2009 19:48:53 +0000 Received: from pws-pc ([81.107.42.185]) by aamtaout03-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20090120194853.UFLH2093.aamtaout03-winn.ispmail.ntl.com@pws-pc> for ; Tue, 20 Jan 2009 19:48:53 +0000 Date: Tue, 20 Jan 2009 19:48:47 +0000 From: Peter Stephenson To: zsh-workers@sunsite.dk Subject: Re: sourcing a sh file in zsh Message-ID: <20090120194847.58a30c9a@pws-pc> In-Reply-To: <090117121501.ZM8940@torch.brasslantern.com> References: <090116075615.ZM21871@torch.brasslantern.com> <200901161939.54651.arvidjaar@newmail.ru> <090116102934.ZM22119@torch.brasslantern.com> <20090117035923.GA64953@redoubt.spodhuis.org> <090116210045.ZM22623@torch.brasslantern.com> <20090117055559.GA60339@redoubt.spodhuis.org> <090117121501.ZM8940@torch.brasslantern.com> X-Mailer: Claws Mail 3.6.1 (GTK+ 2.14.5; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Cloudmark-Analysis: v=1.0 c=1 a=NLZqzBF-AAAA:8 a=qPZFgoojco5pGEYQfbkA:9 a=E81uMkkY76ZP6Wyira5x-XAJkdoA:4 a=LY0hPdMaydYA:10 X-Virus-Scanned: ClamAV 0.92.1/8881/Tue Jan 20 15:48:51 2009 on bifrost X-Virus-Status: Clean On Sat, 17 Jan 2009 12:15:01 -0800 Bart Schaefer wrote: > Regardless I don't think we'd want to do this as yet another setopt. > It's potential can of worms along the lines of ALL_EXPORT, in that > one can end up accidentally applying a specific option context to a > function definition where one didn't (or shouldn't) mean to do so. > I'd lean toward something that works like the "emulation" global, > which is still localized to function scope but which is changable > only by the "emulate" command. > > Combined with allowing "emulate" create a scope and run a command > in that scope, is there anything else you'd need? > > PWS, any comment on how difficult it would be to extend "emulate" in > this way? Would it require promoting emulate to a keyword? I haven't heard anything that sounds particularly difficult, although it obviously needs a firm grip on what's being set at what point. I don't see why emulate should have to behave specially as far as syntax is concerned, as long as its behaviour is well defined. -- Peter Stephenson Web page now at http://homepage.ntlworld.com/p.w.stephenson/