Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160411075056.ZM24247@torch.brasslantern.com>
Date: Mon, 11 Apr 2016 07:50:56 -0700
In-Reply-To: <CAHYJk3SEeghkbpLCE26bG_76nM5PYp9MF68AO1ue00DHTwRV6A@mail.gmail.com>
Comments: In reply to Mikael Magnusson <mikachu@gmail.com>
        "Re: Allow slash in alternation patterns in limited cases?" (Apr 11, 12:22pm)
References: <CAHYJk3TY5kU0fXDkk2iO7kRJhhMTS1f4a9Am1ueN4wCXOQ7Hsg@mail.gmail.com> 
	<160410151105.ZM21544@torch.brasslantern.com> 
	<20160411093738.11406966@pwslap01u.europe.root.pri> 
	<CAHYJk3SEeghkbpLCE26bG_76nM5PYp9MF68AO1ue00DHTwRV6A@mail.gmail.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: Allow slash in alternation patterns in limited cases?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Apr 11, 12:22pm, Mikael Magnusson wrote:
} Subject: Re: Allow slash in alternation patterns in limited cases?
}
} On Mon, Apr 11, 2016 at 10:37 AM, Peter Stephenson
} <p.stephenson@samsung.com> wrote:
} >
} > The only way I can see is effectively to parse it first in the globbing
} > code to treat a complete set of parentheses specially.
} 
} Doesn't this already work as is with pattern matching?

Yes, but so does somestuff(one/thing|another/things)morestuff.  So it's
inconsistent with pattern matching in that a set of parens enclosing the
entire pattern now takes on special semantics.