Re: [BUG] In reference to patch 39815, about (z) flag and $( parse error

[Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>]

Bart Schaefer wrote on Sun, 15 Oct 2017 11:09 -0700:
> On Oct 15,  4:31pm, Sebastian Gniazdowski wrote:
> }
> } It's rather not a bug after all. The cause is an apostrophe in comment.
> } 
> } # '
> } () {
> }         au_arr+=(expand-absolute-path up-line-or-beginning-search)
> } }
> 
> Interesting.

To be clear, the parse in the grandparent message is correct for an
interactive shell with interactivecomments disabled.  (Well, "correct"
considering that the final, multiline string, token is incomplete.)

(z-sy-h uses ${(z)} to parse $PREBUFFER$BUFFER.)

> This points out a different issue:
> 
> torch% setopt cshjunkiequotes
> torch% printf '<%s>\n' ${(z)buf}