From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-38263-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 28780 invoked by alias); 10 Apr 2016 12:11: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: 38263
Received: (qmail 27411 invoked from network); 10 Apr 2016 12:11:20 -0000
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: cbfec7f4-f796c6d000001486-10-570a42e0a76b
Date: Sun, 10 Apr 2016 13:11:08 +0100
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: PATCH: short-circuiting glob exclusion operator
Message-id: <20160410131108.2cdd283d@pwslap01u.europe.root.pri>
In-reply-to: <160409224042.ZM25419@torch.brasslantern.com>
References: <20160321183649.4fd4d72a@pwslap01u.europe.root.pri>
 <160321155421.ZM27019@torch.brasslantern.com>
 <20160322094614.13b07bf4@pwslap01u.europe.root.pri>
 <160326084042.ZM12055@torch.brasslantern.com>
 <20160407211027.2c305cad@ntlworld.com>
 <160407201830.ZM3747@torch.brasslantern.com>
 <20160409192218.3f1d6710@ntlworld.com>
 <CAHYJk3QzmTj_kWZ+L7MDCnW+=Bmfw6UejROKkWoRjNyWyaLW+Q@mail.gmail.com>
 <20160409205142.4d23676a@ntlworld.com>
 <160409224042.ZM25419@torch.brasslantern.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/xq7oPnLjCDTa8Ybc42PyQyYHRY9XB
	D0wBjFFcNimpOZllqUX6dglcGU+/b2EqOMdWsXeKbAPjYtYuRk4OCQETibN/rrNA2GISF+6t
	ZwOxhQSWMko8vBTZxcgFZM9gknjStIIZwjnHKLFzRjMThHOWUWLd/9tADgcHi4CqxOU10iDd
	bAKGElM3zWYEsUWAws3f/4FtEBawkdg3aSpYnFfAXmL7qk5GkFZOASuJyb+qIUZ+Y5b4NXk3
	O0gNv4C+xNW/n5ggrrOXmHnlDFSvoMSPyffAZjILaEls3tbECmHLS2xe85YZ4gN1iRt3d7NP
	YBSehaRlFpKWWUhaFjAyr2IUTS1NLihOSs811CtOzC0uzUvXS87P3cQICeUvOxgXH7M6xCjA
	wajEw7sinzNciDWxrLgy9xCjBAezkgjvSQeucCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8c3e9
	DxESSE8sSc1OTS1ILYLJMnFwSjUwVkcI33zRPvXmn+VTo67cWrPiVOvStF8hxhNEEnfueCg1
	w1lE7JJbY/3CUD7OeQsS3SrEawr6Vl4vy0t4kWLxuWapcrufxFol66LDyrMDFrusl/uy41DV
	94wdl8X7M/ZtPz9D6u76E+8Dzxu93n7VINCh6tLeSouI9yytejnG+qcFTvY9P3fYUomlOCPR
	UIu5qDgRABMDNdVhAgAA

On Sat, 09 Apr 2016 22:40:42 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Apr 9,  8:51pm, Peter Stephenson wrote:
> I think Mikael is asking about specifying both conditions in the *same*
> glob pattern, i.e. **/*~*/foo~*/bar(Y-) such that bar directories are
> short-circuited whereas only paths ending in foo are excluded, but any
> files below a directory foo remain.  Your doc and the comments about
> treating multiple ~ as if they were | seem to imply that both foo and
> bar would be short-circuited in this example.
> 
> Of course one can still write **/*~*/foo~*/bar/* without (Y-).

Right, you have to pick one or the other meaning.

If this becomes important we could force (#e) only to match on
a complete match, which is sort of what it's for.  But I wouldn't
expect this to be a real problem.

pws