From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh workers <zsh-workers@zsh.org>
Subject: Re: Possible parsing bug with alternate for-loop syntax
Date: Sat, 11 Jun 2016 21:21:51 +0200 [thread overview]
Message-ID: <CAHYJk3RYbfA77ir0qgceLjNWi4ZFY=v-dHY3EwhTn_OM6tOPPQ@mail.gmail.com> (raw)
In-Reply-To: <160611113127.ZM13090@torch.brasslantern.com>
On Sat, Jun 11, 2016 at 8:31 PM, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> Doesn't have anything to do with for-loop syntax:
>
> torch% a=hi}; echo $a
> hi}
> torch% {a=hi}; echo $a
> cursh>
>
> It's assignment parsing. The "}" is always considered part of the
> value assigned to the variable.
Ah, you're right, the same thing happens with function parsing as well,
% () {a=hi}
function>
--
Mikael Magnusson
prev parent reply other threads:[~2016-06-11 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 15:48 Mikael Magnusson
2016-06-11 18:31 ` Bart Schaefer
2016-06-11 19:21 ` Mikael Magnusson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHYJk3RYbfA77ir0qgceLjNWi4ZFY=v-dHY3EwhTn_OM6tOPPQ@mail.gmail.com' \
--to=mikachu@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).