From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: zsh-3.1.5-pws-11: _bindkey
Date: Wed, 10 Mar 1999 11:10:16 +0100 [thread overview]
Message-ID: <9903101010.AA42544@ibmth.df.unipi.it> (raw)
In-Reply-To: "Sven Wischnowsky"'s message of "Wed, 10 Mar 1999 10:48:24 NFT." <199903100948.KAA16237@beta.informatik.hu-berlin.de>
Sven Wischnowsky wrote:
> > + compgen -b -M 'r:|-=* r:|=*'
>
> I'd like to ask anyone if we should really do things like this.
> Personally I would prefer to let the user use the global match
> specs for things like this as otherwise the behavor might be somewhat
> unexpected.
Seems to me perfectly OK if it's documented. It's much more natural here
than it is in file names, since the parts of widget names are often similar
to one another, so much so that it's unlikely to produce any completion you
weren't expecting, unless you mistyped.
--- Completion/Builtins/_bindkey.doc Tue Mar 9 18:05:37 1999
+++ Completion/Builtins/_bindkey Wed Mar 10 11:06:07 1999
@@ -1,5 +1,12 @@
#defcomp bindkey
+# Normally, this completes names of zle widgets, whether the builtin ones
+# or ones defined by the user. Note that a - allows a wildcard before it,
+# so h-b-s-b will complete to history-beginning-search-backward. You
+# can alter this by removing the -M ... from the second compgen.
+#
+# Where appropriate, will complete keymaps instead of widgets.
+
if [[ "$words[2]" = -*[DAN]* || "$words[CURRENT-1]" = -*M ]]; then
compgen -s '$(bindkey -l)'
else
--
Peter Stephenson <pws@ibmth.df.unipi.it> Tel: +39 050 844536
WWW: http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy
next prev parent reply other threads:[~1999-03-10 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-10 9:48 Sven Wischnowsky
1999-03-10 10:10 ` Peter Stephenson [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-03-09 17:00 Andrej Borsenkow
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=9903101010.AA42544@ibmth.df.unipi.it \
--to=pws@ibmth.df.unipi.it \
--cc=zsh-workers@sunsite.auc.dk \
/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).