From: Oliver Kiddle <opk@u.genie.co.uk>
To: zsh-workers@sunsite.dk
Subject: PATCH: _bindkey
Date: Fri, 04 May 2001 11:40:23 +0100 [thread overview]
Message-ID: <3AF28717.2C52E766@u.genie.co.uk> (raw)
This makes _bindkey cope with Peter's changes to bindkey in 14046.
The example in the docs (bindkey -rpM viins '^[') isn't completed
properly - the keymap and prefix are completed the wrong way around. I
think the way _arguments works is the better order but then I'd
probably always write this as something like bindkey -rp '^[' -M viins.
Oliver
Index: Completion/Zsh/Command/_bindkey
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Zsh/Command/_bindkey,v
retrieving revision 1.1
diff -u -r1.1 _bindkey
--- Completion/Zsh/Command/_bindkey 2001/04/02 11:25:59 1.1
+++ Completion/Zsh/Command/_bindkey 2001/05/04 10:17:14
@@ -14,7 +14,7 @@
'(-v -a -M -l -D -A -N -p)-e[select emacs keymap and bind it to main]' \
'(-e -a -M -l -D -A -N -p)-v[select viins keymap and bind it to main]' \
'(-e -v -M -l -D -A -N -p)-a[select vicmd keymap]' \
- '(-e -v -a -l -D -A -N -p)-M[specify keymap to select]:keymap:->keymap' \
+ '(-e -v -a -l -D -A -N)-M[specify keymap to select]:keymap:->keymap' \
'(-e -v -a -M -D -A -N -m -p -r -s -R *)-l[list existing keymap names]' \
'(-e -v -a -d -A -N -m -r -s -R *)-L[output in form of bindkey commands]' \
'(-e -v -a -l -D -A -N -m -p -r -s -R *)-d[delete existing keymaps and reset to default state]' \
@@ -22,8 +22,8 @@
'(-e -v -a -M -l -L -d -D -N -m -p -r -s -R *)-A[create alias to keymap]:old-keymap:->keymap:new-keymap:->keymap' \
'(-e -v -a -M -l -L -d -D -A -m -p -r -s -R *)-N[create new keymap]:new-keymap:->keymap:old-keymap to copy:->keymap' \
'(-l -L -d -D -A -N -p -r -s -r -R *)-m[add builtin meta-key bindings to selected keymape]' \
- '(-e -v -a -M -d -D -A -N -m -r -s -R *)-p[list bindings which have given key sequence as a prefix]:key sequence' \
- '(-l -L -d -D -A -N -m -p -s *)-r[unbind specified in-strings]:*:in-string' \
+ '(-e -v -a -d -D -A -N -m -s -R *)-p[list bindings which have given key sequence as a prefix]:key sequence' \
+ '(-l -L -d -D -A -N -m -s *)-r[unbind specified in-strings]:*:in-string' \
'(-l -L -d -D -A -N -m -p -r *)-s[bind each in-string to each out-string]:*:key string' \
'(-e -v -a -M -l -L -d -D -A -N -m -p)-R[interpret in-strings as ranges]' \
'(-l -L -d -A -N -m -p -r -s)*::widgets:->widget' && ret=0
_____________________________________________________________________
This message has been checked for all known viruses by the
MessageLabs Virus Scanning Service. For further information visit
http://www.messagelabs.com/stats.asp
next reply other threads:[~2001-05-04 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 10:40 Oliver Kiddle [this message]
2001-05-04 10:55 ` 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=3AF28717.2C52E766@u.genie.co.uk \
--to=opk@u.genie.co.uk \
--cc=zsh-workers@sunsite.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).