Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: spurious 'case' parse error

X-seq: zsh-workers 41746
From: Martijn Dekker <martijn@xxxxxxxx>
To: zsh-workers@xxxxxxx
Subject: Re: spurious 'case' parse error
Date: Fri, 22 Sep 2017 17:59:37 +0100
In-reply-to: <170922084246.ZM22988@torch.brasslantern.com>
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
References: <6fb7e839-48ce-51a4-1d64-bbbf498c5bfb@inlv.org> <170922084246.ZM22988@torch.brasslantern.com>

Op 22-09-17 om 16:42 schreef Bart Schaefer:
> That's almost certainly happening because
> 
>     case xecho in
>     (x|y)echo)echo ok;;
>     esac
> 
> is valid syntax for zsh, so (x)echo is being parsed as a pattern and then
> the closing paren is found to be missing.

That makes sense. Also, when zsh is launched as 'sh', the parsing error
does not occur. Report withdrawn. Sorry for the noise!

- M.

References:
- spurious 'case' parse error
  - From: Martijn Dekker
- Re: spurious 'case' parse error
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author