From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1560 invoked by alias); 11 Feb 2012 21:08:44 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 30209 Received: (qmail 18140 invoked from network); 11 Feb 2012 21:08:42 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <120211130818.ZM10122@torch.brasslantern.com> Date: Sat, 11 Feb 2012 13:08:18 -0800 In-reply-to: <20120210210411.4e14cc3f@pws-pc.ntlworld.com> Comments: In reply to Peter Stephenson "Re: Bug with bash emulation regarding ':'" (Feb 10, 9:04pm) References: <20120129183644.6d49d237@pws-pc.ntlworld.com> <120131202909.ZM6076@torch.brasslantern.com> <120201082929.ZM7032@torch.brasslantern.com> <20120205201133.3bcd2b7f@pws-pc.ntlworld.com> <120205132146.ZM7315@torch.brasslantern.com> <20120210210411.4e14cc3f@pws-pc.ntlworld.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: Bug with bash emulation regarding ':' MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Feb 10, 9:04pm, Peter Stephenson wrote: } } It took some thinking about, but I think the following is about the most } minimal code. Nice. } Even allowing for the fact that explicit splitting is } separate from sh-wordsplitting (it's a stronger condition), it needed a } third flag to distinguish the cases... } } - SHWORDSPLIT is on normally. } - SHWORDSPLIT isn't on, but is required by a recursive substitution. } - SHWORDSPLIT needs to be forced off by a recursive substitution. I agree that this covers everything. (It's a bit convoluted that it's possible for both PF_SHWORDSPLIT and PF_NOSHWORDSPLIT to be true at the same time, but .) Incidentally, are we in any danger of conflict with the "PF_" prefix as used in for protocol families? PF_UNIX, PF_INET, etc.? } There's now no temporary setting of SHWORDSPLIT itself [...] } } I don't know if this helps with the other issues you mentioned. I believe it should -- the other issues all stemmed from modifying and then restoring opts[SHWORDPSLIT], which this eliminates.