From: Bart Schaefer <schaefer@brasslantern.com>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: "Lawrence Velázquez" <larryv@zsh.org>, zsh-workers@zsh.org
Subject: Re: [PATCH?] Nofork and removing newlines
Date: Thu, 7 Mar 2024 11:02:36 -0800 [thread overview]
Message-ID: <CAH+w=7ZzTQc7azMcCB_saaH+DvsoRARV_NKjUJzmA4S887O5BA@mail.gmail.com> (raw)
In-Reply-To: <CAHYJk3SDs7Sz_6TnMTC7e9cf+C8XzJGs=_Cz7wYkK+p4ChEwgg@mail.gmail.com>
On Thu, Mar 7, 2024 at 12:26 AM Mikael Magnusson <mikachu@gmail.com> wrote:
>
> On 3/7/24, Lawrence Velázquez <larryv@zsh.org> wrote:
> >
> > % print ${:-{}x}
> > {}x
> > % print "${:-{}x}"
> > {x}
>
> This is not really an effect of quoting per se, really it's just luck
> that the unquoted form works. [...] Your example only
> happens to pass the parsing stage because the braces are balanced
> which they have no inherent reason to do in what is supposedly a
> string literal.
It passes the balanced braces because this:
% print ${:-{a,b,c}x}
ax bx cx
And because this:
% print {}
{}
I'm leaving this in the same discussion thread because I just noticed
that ${|...} and ${ cmd } do not really respect the
IGNORE_CLOSE_BRACES option. Setting that option changes handling of
unbalanced braces (and I'm not yet sure if it does so in a sensible
way) but does not force use of the semicolon e.g. in ${ cmd; } which
theoretically it should. Is this worth trying to work in?
next prev parent reply other threads:[~2024-03-07 19:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 5:52 Bart Schaefer
2024-03-05 6:56 ` Stephane Chazelas
2024-03-05 22:48 ` Bart Schaefer
2024-03-06 17:57 ` Stephane Chazelas
2024-03-06 19:45 ` Bart Schaefer
2024-03-06 22:22 ` Mikael Magnusson
2024-03-06 22:42 ` Bart Schaefer
2024-03-07 4:53 ` Bart Schaefer
2024-03-07 7:02 ` Lawrence Velázquez
2024-03-07 8:09 ` ${<file} (Was: [PATCH?] Nofork and removing newlines) Stephane Chazelas
2024-03-08 1:29 ` [PATCH?] Nofork and removing newlines Bart Schaefer
2024-03-08 22:15 ` Oliver Kiddle
2024-03-08 23:28 ` Bart Schaefer
2024-03-09 20:43 ` Oliver Kiddle
2024-03-10 6:11 ` Bart Schaefer
2024-03-12 17:54 ` Bart Schaefer
2024-03-12 23:19 ` Oliver Kiddle
2024-03-13 4:13 ` Bart Schaefer
2024-03-14 22:15 ` Oliver Kiddle
2024-03-15 8:42 ` Stephane Chazelas
2024-03-27 1:16 ` Bart Schaefer
2024-03-27 7:05 ` Bart Schaefer
2024-03-07 7:10 ` Stephane Chazelas
2024-03-08 0:37 ` Bart Schaefer
2024-03-07 6:52 ` Lawrence Velázquez
2024-03-07 8:26 ` Mikael Magnusson
2024-03-07 19:02 ` Bart Schaefer [this message]
2024-04-02 6:45 ` Lawrence Velázquez
2024-03-06 19:43 ` Stephane Chazelas
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=7ZzTQc7azMcCB_saaH+DvsoRARV_NKjUJzmA4S887O5BA@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=larryv@zsh.org \
--cc=mikachu@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).