From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-37004-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 9546 invoked by alias); 28 Oct 2015 16:00:23 -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: 37004
Received: (qmail 25740 invoked from network); 28 Oct 2015 16:00:20 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.0
X-AuditID: cbfec7f5-f794b6d000001495-a1-5630f11079ec
Date: Wed, 28 Oct 2015 15:59:43 +0000
From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] Index of element after width of characters
Message-id: <20151028155943.14acea0b@pwslap01u.europe.root.pri>
In-reply-to:
 <CAKc7PVCZRJyxF_ysPS6eqNbHpbwYJ+yem-EL3pVLAtXKkrGhVQ@mail.gmail.com>
References:
 <CAKc7PVC4LFGnBJau3gWuws3bTgc+zcnEE+o-B8ZmKEEWa8Kpog@mail.gmail.com>
 <CAH+w=7b1RQDPWw0u7NSDs9wdxC-rCQYvyXadKCd1pdNXEdFuXA@mail.gmail.com>
 <CAKc7PVCGFJSZbiHDpJHivFco8J3SfHDesdjJoTzAY-sR4K5++w@mail.gmail.com>
 <CAKc7PVD=H+e9tyrVSM-TbwzFjKs=cAygNC0yzkO=uuNFEH7PjQ@mail.gmail.com>
 <CAKc7PVAffA-TBHtaCdcYhMnPpDFv26cnYjTFafYBL1ib=rJKXA@mail.gmail.com>
 <CAHYJk3Qzr6LEYMXXoHbTuiAqc8fadiP8A6uQyS77w3KkoDo7bQ@mail.gmail.com>
 <CAKc7PVCZRJyxF_ysPS6eqNbHpbwYJ+yem-EL3pVLAtXKkrGhVQ@mail.gmail.com>
Organization: Samsung Cambridge Solution Centre
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu)
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsVy+t/xy7oCHw3CDHb/k7M42PyQyYHRY9XB
	D0wBjFFcNimpOZllqUX6dglcGT+vrmIp2MVSsXZfSAPjGeYuRk4OCQETiUMHX0DZYhIX7q1n
	62Lk4hASWMooceLVWShnBpPEsX+P2UCqhAS2MUrsO5TZxcjBwSKgKjFjRTxImE3AUGLqptmM
	ILaIgJbEjpMnmUBsYQF7iWUrjrOD2LxA9vu+d6wgNqdAsMTbnl9Q8/8wS5xc+QgswS+gL3H1
	7ycmiIvsJWZeOcMI0Swo8WPyPRYQmxloweZtTawQtrzE5jVvmSFuU5e4cXc3+wRGoVlIWmYh
	aZmFpGUBI/MqRtHU0uSC4qT0XCO94sTc4tK8dL3k/NxNjJCQ/bqDcekxq0OMAhyMSjy8AlsM
	woRYE8uKK3MPMUpwMCuJ8M57AxTiTUmsrEotyo8vKs1JLT7EKM3BoiTOO3PX+xAhgfTEktTs
	1NSC1CKYLBMHp1QDY8y1b/nNb75NP9R7rlmmSdX26NfCsx3b48Lf8wrd8pxv9ulJhYfX5jUP
	bJ1eTOf+8ljo83ebD9w/lSSs1aOXtXKzfW98ckpGc/rzY0Fc3+/J3pfZFifCWb/3mdVP26UR
	GvdDRNaJz/rj9khlAp/aFacP29wbNn+cpKewhOtA0qyQFPcHK6bwSiqxFGckGmoxFxUnAgDg
	EhjjVQIAAA==

On Wed, 28 Oct 2015 16:46:00 +0100
Sebastian Gniazdowski <sgniazdowski@gmail.com> wrote:
> I can resign from the "," and stay with "<" and ">" if Bart agrees.
> The comma would be more complicated than the rest, having 3 possible
> values: index, -1, empty string. Having only "<" and ">" it's easy to
> detect that the limit doesn't divide any char in half:

Mikael's right, actually --- this is an indexing problem and more
consistently done with subscripts.  It should actually be simpler than
the existing code for space-delimited words in scalars.

pws