From: Bart Schaefer <schaefer@brasslantern.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: zsh-users@zsh.org
Subject: Re: quoting question
Date: Tue, 12 Sep 2023 13:23:56 -0700 [thread overview]
Message-ID: <CAH+w=7YM_pc_LutJOfsYQnPs=QXjDfjHJy=7aDqh7hVU5cM6-g@mail.gmail.com> (raw)
In-Reply-To: <8218b46632e67c16b18187612d0b0d51491cd30b.camel@ntlworld.com>
On Tue, Sep 12, 2023 at 1:08 PM Peter Stephenson
<p.w.stephenson@ntlworld.com> wrote:
>
> It looks like we're not couting brace pairs within quotes the way we do
> outside. I suppose the reason for that is something along the lines of:
> if we encounter a "{" inside quotes itʼs just a reguler character so
> doesnʼt have a special syntax associated. But the inconvenience of
> counting braces differently just because youʼve added double quotes surely
> outweighs that.
I went to incredible lengths with the ${| ... } parsing to get around
this very thing.
Refer workers/51907
(https://www.zsh.org/mla/workers/2023/msg00636.html) for Mikael's
argument of why this should NOT be changed.
In any case this patch conflicts with workers/51987 ... it appears
possible to merge them and all my D10 tests still pass, so not a great
problem.
next prev parent reply other threads:[~2023-09-12 20:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 18:45 Jim
2023-09-12 20:06 ` Bart Schaefer
2023-09-13 2:50 ` Jim
2023-09-13 3:41 ` Bart Schaefer
2023-09-13 15:09 ` Debug zsh (was: Re: quoting question) Pier Paolo Grassi
2023-09-13 15:28 ` Mikael Magnusson
2023-09-13 11:28 ` quoting question Jim
2023-09-13 16:11 ` Bart Schaefer
2023-09-12 20:07 ` Peter Stephenson
2023-09-12 20:23 ` Bart Schaefer [this message]
2023-09-12 20:29 ` Bart Schaefer
2023-09-13 1:56 ` Mikael Magnusson
2023-09-13 8:50 ` Peter Stephenson
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=7YM_pc_LutJOfsYQnPs=QXjDfjHJy=7aDqh7hVU5cM6-g@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=p.w.stephenson@ntlworld.com \
--cc=zsh-users@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).