zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Marlon Richert <marlon.richert@gmail.com>,
	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 20:08:28 -0700	[thread overview]
Message-ID: <CAH+w=7YehxT68rwQusA10=j9S=-yU13=40nMdZqQ3xBb_JXoCw@mail.gmail.com> (raw)
In-Reply-To: <CAHYJk3SyFw0YEuhVNdwz8dnkzGiR27W-7P5Y=Mi3GRwiHZvwMA@mail.gmail.com>

On Thu, Aug 5, 2021 at 5:55 PM Mikael Magnusson <mikachu@gmail.com> wrote:
>
> On 8/6/21, Bart Schaefer <schaefer@brasslantern.com> wrote:
> > On Wed, Aug 4, 2021 at 11:18 PM Marlon Richert <marlon.richert@gmail.com>
> >> 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} ?
>
> braceccl works on the byte level only so it's not usable for multibyte
> codepoints etc.

Hm, it might make more sense to enable multibyte in braceccl than to
disable quoting in {a..z}.  (Admittedly, it also might be more
difficult.)


  reply	other threads:[~2021-08-06  3:09 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
2021-08-06  0:55       ` Mikael Magnusson
2021-08-06  3:08         ` Bart Schaefer [this message]
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=7YehxT68rwQusA10=j9S=-yU13=40nMdZqQ3xBb_JXoCw@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=marlon.richert@gmail.com \
    --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).