From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: PATCH: configurability of pattern characters, part 1
Date: Fri, 31 May 2013 23:22:23 -0700 [thread overview]
Message-ID: <130531232223.ZM13592@torch.brasslantern.com> (raw)
In-Reply-To: <20130601002954.0e30d7b9@pws-pc.ntlworld.com>
On Jun 1, 12:29am, Peter Stephenson wrote:
}
} The second step, to follow: now we have the "zpc_special" array, it will
} be possible (and fairly straightforward) to introduce a special variable
} to indicate pattern characters that should be turned off
Possible alternative idea -- use the enable/disable builtins?
disable -p '^' '(' '+('
(Choose another switch if you don't like -p for pattern.)
I suppose that's harder to set/restore on within/without a local scope.
On the other hand I've frequently wished that some internal tables were
scope-able; e.g., making the $functions special variable a local has
subtle undesirable side-effects on autoloaded functions, but if the
underlying table itself could be localized, those would go away.
} We'll need to set the new shell variable(s) locally to empty for
} completion.
Hmm, that's another problem with the enable/disable idea ... or is it?
"emulate -R zsh -c 'autoload _main_complete'" should do the trick ...?
} I think also "emulate" should clear them (locally for "emulate -L") to
} present a pristine pattern environment for emulation.
I agree ... which for me is an argument *against* using variables for
this. I know emulation modes already play with the special-ness of
things like HISTCHARS and MANPATH, but it doesn't actually go so far
as creating empty locals for them.
Speaking of HISTCHARS, do we agree that it'd be a bad idea to be able
to swap around which characters have what glob semantics? E.g., it's
OK if * means only "*", but you can't make % mean "match any number of
any character".
--
Barton E. Schaefer
next prev parent reply other threads:[~2013-06-01 6:22 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 [this message]
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
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=130531232223.ZM13592@torch.brasslantern.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).