From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2183 invoked from network); 13 Feb 2001 09:58:07 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 13 Feb 2001 09:58:07 -0000 Received: (qmail 9967 invoked by alias); 13 Feb 2001 09:57:48 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 13461 Received: (qmail 9952 invoked from network); 13 Feb 2001 09:57:39 -0000 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) From: "Andrej Borsenkow" To: Subject: RE: More incompatibility :-) RE: PATCH: 3.1.9-dev-8: Re: Word splitting in zsh Date: Tue, 13 Feb 2001 12:57:34 +0300 Message-ID: <001601c095a3$63928b10$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <1010213092648.ZM26163@candle.brasslantern.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 > > They are saved, set, and restored in a small block around the call to > multsub(), and otherwise referenced only on first entry to paramsubst(). > They have no effect other than to override the current setting of the > shwordsplit option. That does mean that > > print ${=foo+"$(unsetopt shwordsplit;print -l $bar)"} > > actually *does* split the value of $bar within the command subst. Hmm. > Yep. That is exactly what I meant. I'm not sure what is current status, but I always assumed that any flag applies to current value only and not propagates to nested substitutions. At least this sounds logical. -andrej