From: Bart Schaefer <schaefer@brasslantern.com>
To: linuxtechguy@gmail.com
Cc: devs <zsh-workers@zsh.org>
Subject: Re: Strange brace(}) behavior with multiple for loops
Date: Mon, 14 Nov 2022 10:08:01 -0800 [thread overview]
Message-ID: <CAH+w=7YMxtUUqmisTZ2=t+vNC6bBv6a+FaoGOV0yUm5gHgW9=g@mail.gmail.com> (raw)
In-Reply-To: <CA+rB6G++kshQjMqdw--T38S1thcyhPmGHLN21beUuPjas1Fp1g@mail.gmail.com>
On Mon, Nov 14, 2022 at 9:56 AM Jim <linux.tech.guy@gmail.com> wrote:
>
> Depending on how I terminate the loops(see above) the anonymous function either
> works or fails if using 3 braces(}}}) togather(no spaces).
>
> Q: Is this a bug, or am I missing something?
I suppose it's technically a bug, but "}" is either a token or not
depending on context, so it's generally a good idea to put spaces
around them, just like in the previous thread about alias expansions.
prev parent reply other threads:[~2022-11-14 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 17:54 Jim
2022-11-14 18:08 ` Bart Schaefer [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='CAH+w=7YMxtUUqmisTZ2=t+vNC6bBv6a+FaoGOV0yUm5gHgW9=g@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=linuxtechguy@gmail.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).