From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-30181-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 5964 invoked by alias); 5 Feb 2012 21:22:07 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 30181
Received: (qmail 15468 invoked from network); 5 Feb 2012 21:22:04 -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 <schaefer@brasslantern.com>
Message-id: <120205132146.ZM7315@torch.brasslantern.com>
Date: Sun, 05 Feb 2012 13:21:46 -0800
In-reply-to: <20120205201133.3bcd2b7f@pws-pc.ntlworld.com>
Comments: In reply to Peter Stephenson <p.w.stephenson@ntlworld.com>
 "Re: Bug with bash emulation regarding ':'" (Feb  5,  8:11pm)
References:
 <CAMP44s2Zo5U=RVuznntDOFeqUZeJdmg1XfHMg4egu-1PRjnkKA@mail.gmail.com>
	<20120129183644.6d49d237@pws-pc.ntlworld.com>
	<120131202909.ZM6076@torch.brasslantern.com>
	<120201082929.ZM7032@torch.brasslantern.com>
	<20120205201133.3bcd2b7f@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 5,  8:11pm, Peter Stephenson wrote:
}
} How about this for the original problem?  It's at least a simple change,
} tied to one documented C variable.  It doesn't address the related areas
} you mentioned, but I think those are less important, because they don't
} affect Bourne/POSIX emulation

Seems reasonable to me.  I was hunting for a way to do it without adding
another global, but what you've done is probably the most expedient.

(I wonder if changing the boolean "split" parameter to multsub() into a
set of bitflags would suffice.)

I don't have anything more to add on the rest of this discussion, a this
point ...