zsh-workers
 help / color / mirror / code / Atom feed
From: Andrej Borsenkow <bor@itsmx1.mow.sni.de>
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: zsh-3.1.5-pws-11: _bindkey
Date: Tue, 9 Mar 1999 20:00:04 +0300 (MSK)	[thread overview]
Message-ID: <Pine.SV4.4.10.9903091958390.10629-100000@itsrm2.mowp.siemens.ru> (raw)

Trivial addition.

cheers
/andrej


--- Completion/Builtins/_bindkey	Tue Mar  9 16:26:35 1999
+++ /home/bor/.zsh.d/Completion/Builtins/_bindkey	Tue Mar  9 19:55:36 1999
@@ -3,5 +3,5 @@
 if [[ "$words[2]" = -*[DAN]* || "$words[CURRENT-1]" = -*M ]]; then
   compgen -s '$(bindkey -l)'
 else
-  compgen -b
+  compgen -b -M 'r:|-=* r:|=*'
 fi


             reply	other threads:[~1999-03-09 17:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-09 17:00 Andrej Borsenkow [this message]
1999-03-10  9:48 Sven Wischnowsky
1999-03-10 10:10 ` 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=Pine.SV4.4.10.9903091958390.10629-100000@itsrm2.mowp.siemens.ru \
    --to=bor@itsmx1.mow.sni.de \
    --cc=borsenkow.msk@sni.de \
    --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).