From: Marlon Richert <marlon.richert@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Why does {..} expansion using 'bindkey' quoting, but {,} and BRACE_CCL don't quote at all?
Date: Thu, 5 Aug 2021 09:17:38 +0300 [thread overview]
Message-ID: <CAHLkEDvmQAN1w5An46hP0_b9dv13om6_Yms3uPmnDOT_CN0uvQ@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7YmBRdW51WA=wY34kz_Si1ScnSOKzvaFPJO-eDGQ4G1kg@mail.gmail.com>
On Wed, Aug 4, 2021 at 6:52 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Wed, Aug 4, 2021 at 12:05 AM Marlon Richert <marlon.richert@gmail.com> wrote:
> >
> > Is there a reason for this inconsistency? Why not always produce
> > quoted or unquoted output?
> >
> > Also, why bindkey-style quoting? Wouldn't ${(q+)}-style quoting be
> > more convenient, since it's more straightforward to "unquote"?
>
> The answer to "why doesn't feature A take advantage of feature B" is
> often "because A was developed long before B".
>
> I believe that's the case in both instances here. BRACE_CCL and {x,y}
> existed before {a..z}, and {a..z} existed before $'..'. Old code was
> never updated to be consistent with newer code, either from simply
> being overlooked, or for backwards compatibility.
I just wish {a..z} didn't use quoting at all. :)
I understand, though, that it's hard to change at this point, because
of backwards compatibility.
How would you feel about adding a shell option to make {a..z}
unquoted? (Or failing that, an option to make all of them
$'..'-quoted.)
next prev parent reply other threads:[~2021-08-05 6:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 7:04 Marlon Richert
2021-08-04 15:52 ` Bart Schaefer
2021-08-05 6:17 ` Marlon Richert [this message]
2021-08-05 23:36 ` Bart Schaefer
2021-08-06 0:55 ` Mikael Magnusson
2021-08-06 3:08 ` Bart Schaefer
2021-08-07 19:35 ` Marlon Richert
2021-08-08 0:09 ` Mikael Magnusson
2021-08-10 19:21 ` Marlon Richert
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=CAHLkEDvmQAN1w5An46hP0_b9dv13om6_Yms3uPmnDOT_CN0uvQ@mail.gmail.com \
--to=marlon.richert@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).