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-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) 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.1
X-AuditID: cbfec7f5-f792a6d000001302-2b-570baba09279
Date: Mon, 11 Apr 2016 14:50:21 +0100
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: Allow slash in alternation patterns in limited cases?
Message-id: <20160411145021.6bc5c31a@pwslap01u.europe.root.pri>
In-reply-to:
 <CAHYJk3TKQx4pB7uKjxwVdU+QQyeJTxo7qj6w0Xibq2V7J_Qsqw@mail.gmail.com>
References:
 <CAHYJk3TY5kU0fXDkk2iO7kRJhhMTS1f4a9Am1ueN4wCXOQ7Hsg@mail.gmail.com>
 <160410151105.ZM21544@torch.brasslantern.com>
 <20160411093738.11406966@pwslap01u.europe.root.pri>
 <CAHYJk3SEeghkbpLCE26bG_76nM5PYp9MF68AO1ue00DHTwRV6A@mail.gmail.com>
 <20160411112941.579d8157@pwslap01u.europe.root.pri>
 <CAHYJk3QkC_jDq94ax2vMZUCaU2iELFO7kk49ogQUg-qafDtgPA@mail.gmail.com>
 <20160411120716.06a6d1c9@pwslap01u.europe.root.pri>
 <CAHYJk3Qc8WsRAxav6wT8MmoEKj-hDByAA3ZCWHHbTt=+CaUQxQ@mail.gmail.com>
 <20160411133145.486788a5@pwslap01u.europe.root.pri>
 <CAHYJk3TKQx4pB7uKjxwVdU+QQyeJTxo7qj6w0Xibq2V7J_Qsqw@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+NgFjrHLMWRmVeSWpSXmKPExsVy+t/xq7oLVnOHG5y7a25xsPkhkwOjx6qD
	H5gCGKO4bFJSczLLUov07RK4Mp5cn8FcMJW14vF+wwbGiSxdjBwcEgImEq+Wu3UxcgKZYhIX
	7q1n62Lk4hASWMoo8X1VI5Qzg0niyt4nrBDOOUaJ1esvM0I4Zxklds+4xAwyikVAVeLTWkeQ
	UWwChhJTN81mBLFFgMLN3/+xgNjCAk4Srx6eZQOxeQXsJZb8+cQOYnMKBEv0br7ODGILCXxj
	kfj0UR7E5hfQl7j69xMTxHn2EjOvnGGE6BWU+DH5HthMZgEtic3bmlghbHmJzWveQs1Rl7hx
	dzf7BEbhWUhaZiFpmYWkZQEj8ypG0dTS5ILipPRcI73ixNzi0rx0veT83E2MkFD+uoNx6TGr
	Q4wCHIxKPLwO17jChVgTy4orcw8xSnAwK4nwRizjDhfiTUmsrEotyo8vKs1JLT7EKM3BoiTO
	O3PX+xAhgfTEktTs1NSC1CKYLBMHp1QDo7Wr8NET+uEb5RW7L1d/3c2UX8zg6P4k9K5rvbKD
	q8mhjFiFh8ldM1d//OI60SG465GVgL6CuyzD1WSL038W5RWpLto11fR2dejlU/0GBXen7joz
	8eHPjSkuf/ar9jNejJliwnno7EP3lQYW916dvZ509jQjn6bYGjt7oTrbE+prZlsr72XXV2Ip
	zkg01GIuKk4EAJfw/RhhAgAA
X-Seq: zsh-workers 38278

On Mon, 11 Apr 2016 15:45:02 +0200
Mikael Magnusson <mikachu@gmail.com> wrote:
> On Mon, Apr 11, 2016 at 2:31 PM, Peter Stephenson
> <p.stephenson@samsung.com> wrote:
> > No, expressions like (foo|bar) are *only* handled by the pattern
> > matcher.  The scanner's sole responsibility is to tell the pattern
> > matcher whether or not it should stop if it sees a "/".
> 
> Ah, that explains it :). Thanks.

To be unhelpfully pedantic... actually, there's one exception, which is
that (.../) is handled specially so you can stick # or ## after it.
That's a special case in parsecomplist(), which looks a little like
what you're trying to do.

pws