zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Marlon Richert <marlon.richert@gmail.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 16:36:10 -0700	[thread overview]
Message-ID: <CAH+w=7aCFe8ofQTbcz13pK1LGKQ9vDt0bLuavOhtGGBL_2hAFA@mail.gmail.com> (raw)
In-Reply-To: <CAHLkEDvmQAN1w5An46hP0_b9dv13om6_Yms3uPmnDOT_CN0uvQ@mail.gmail.com>

On Wed, Aug 4, 2021 at 11:18 PM Marlon Richert <marlon.richert@gmail.com> wrote:
>
> I just wish {a..z} didn't use quoting at all. :)

Re-reading the doc for this, {a..z} is guaranteed to produce PRINTABLE
output, which is not true of the other variations of brace expansion.

> How would you feel about adding a shell option to make {a..z}
> unquoted?

Ambivalent.  If you're going to set an option anyway, why can't you
use BRACE_CCL and {a-z} ?

> (Or failing that, an option to make all of them
> $'..'-quoted.)

That, I think not.  You've already demonstrated that it's simple to
add the quoting ... and in what circumstance would you want the brace
expansion quoted, but the word in which it's embedded, unquoted?


  reply	other threads:[~2021-08-05 23:37 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
2021-08-05 23:36     ` Bart Schaefer [this message]
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='CAH+w=7aCFe8ofQTbcz13pK1LGKQ9vDt0bLuavOhtGGBL_2hAFA@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=marlon.richert@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).