Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: parsing empty alternatives: case foo|) :;;
- X-seq: zsh-workers 41502
- From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
- To: Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
- Subject: Re: parsing empty alternatives: case foo|) :;;
- Date: Mon, 07 Aug 2017 15:26:49 +0100
- Cc: zsh-workers@xxxxxxx
- Cms-type: 201P
- In-reply-to: <20170807135559.odtceysgqn5qeqql@tarpaulin.shahaf.local2>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- Organization: Samsung Cambridge Solution Centre
- References: <CGME20170807135641epcas3p4bc0a64f832ae7fcd76051ac198722045@epcas3p4.samsung.com> <20170807135559.odtceysgqn5qeqql@tarpaulin.shahaf.local2>
On Mon, 7 Aug 2017 13:55:59 +0000
Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx> wrote:
> % case '' in (foo|) echo yes;; esac
> yes
> % case '' in foo|) echo yes;; esac
> zsh: parse error near `)'
>
> Why does the second case fail to parse? We (IRC) don't see any ambiguity
> in it.
I haven't checked, but I think it looks like a pipe --- at that point we
haven't gone further down the case-specific code so that it parses the
line specially.
pws
Messages sorted by:
Reverse Date,
Date,
Thread,
Author