From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: PATCH: configurability of pattern characters, part 1
Date: Mon, 3 Jun 2013 08:05:22 -0700 [thread overview]
Message-ID: <CAH+w=7advMYcjCGL1yvZN2BvBV1iN20Nnm0jsoQ+UXQuJ1RiOg@mail.gmail.com> (raw)
In-Reply-To: <20130603094014.4728e466@pwslap01u.europe.root.pri>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
On Mon, Jun 3, 2013 at 1:40 AM, Peter Stephenson
<p.stephenson@samsung.com>wrote:
> On Sun, 02 Jun 2013 00:16:27 -0700
> Bart Schaefer <schaefer@brasslantern.com> wrote:
> > % setopt kshglob
> > % disable -p '+('
> > % setopt kshglob
> >
> > Does the setopt re-enable '+(' or does it remain disabled?
>
> It remains disabled: that's a separate set of controls.
OK, so one way to think about this is that "disable" controls whether the
syntax is available, and setopt controls whether the syntax is used.
Earlier, though, you said:
> If you want to be able to enable or disable every pattern separetely, you
> "setopt extendedglob kshglob noshglob" first.
Is the word "first" significant there? E.g., does that mean that if I do
% unsetopt kshglob
% disable -p '+('
% setopt kshglob
that '+(' will be enabled? (I know, I could apply the patch and try it,
but I'm interested in the intentions behind it.)
next prev parent reply other threads:[~2013-06-03 15:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 23:29 Peter Stephenson
2013-06-01 6:22 ` Bart Schaefer
2013-06-01 20:18 ` Peter Stephenson
2013-06-02 7:16 ` Bart Schaefer
2013-06-03 8:40 ` Peter Stephenson
2013-06-03 15:05 ` Bart Schaefer [this message]
2013-06-03 15:31 ` Peter Stephenson
2013-06-01 23:09 ` PATCH: configurability of pattern characters, part 2 Peter Stephenson
2013-06-04 6:45 ` Bart Schaefer
2013-06-04 8:44 ` Peter Stephenson
2013-06-04 14:50 ` Bart Schaefer
2013-06-04 15:09 ` Peter Stephenson
2013-06-09 18:06 ` 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=7advMYcjCGL1yvZN2BvBV1iN20Nnm0jsoQ+UXQuJ1RiOg@mail.gmail.com' \
--to=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).