zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-users@zsh.org
Subject: Re: quoting question
Date: Wed, 13 Sep 2023 09:50:42 +0100 (BST)	[thread overview]
Message-ID: <1759298512.3842329.1694595042396@mail.virginmedia.com> (raw)
In-Reply-To: <CAHYJk3Rw6g55DeM1ZfL+h1JX_TQjGHQA_G-656CJ62=to73PnQ@mail.gmail.com>

> On 13/09/2023 02:56 Mikael Magnusson <mikachu@gmail.com> wrote:
> On 9/12/23, Bart Schaefer <schaefer@brasslantern.com> wrote:
> > On Tue, Sep 12, 2023 at 1:23 PM Bart Schaefer <schaefer@brasslantern.com>
> > wrote:
> >>
> >> Refer workers/51907
> >
> > Incidentally your patch will also change the way the PS2 prompt
> > reports %_ -- for example, it will say it's in a brace expansion even
> > when ignorebraces means that brace expansion is disabled.
> 
> I think it's completely wrong to do this, it becomes impossible to
> write { inside a ${:-here} expansion:
> % echo "${:-{{{{}"
> <dquote braceparam braceparam braceparam braceparam dquote:~code/zsh>%
> % echo "${:-\{\{\{\{}"
> <dquote braceparam braceparam braceparam braceparam dquote:~code/zsh>%
> 
> And even if it was possible with extra quoting, we can't just break
> existing strings that happen to have { in them. { inside "" should be
> completely non-special.

If there's a significant knock-on effect, we'll certainly have to leave it alone.

pws


      reply	other threads:[~2023-09-13  8:52 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
2023-09-12 20:29     ` Bart Schaefer
2023-09-13  1:56       ` Mikael Magnusson
2023-09-13  8:50         ` Peter Stephenson [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=1759298512.3842329.1694595042396@mail.virginmedia.com \
    --to=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).