From: "Ilya N. Golubev" <gin@mo.msk.ru>
Subject: key bindings reported incorrectly
Date: Wed, 19 Jul 2006 18:03:27 +0400 [thread overview]
Message-ID: <278xmpite8.fsf@mo.msk.ru> (raw)
Versions: 20.7, 21.4a
Environment: viper enabled.
In help buffer formed by `f1 b', when viper vi movement mode is in
effect, `f1 k N' reports:
N runs the command viper-search-Next
which is an interactive compiled Lisp function in `viper-cmd'.
(viper-search-Next ARG)
So does `f1 b' report.
Actually `N' does nothing in that buffer. `/' was already invoked.
In this case `viper-search-Next', if ever invoked, always either
changes point or outputs <Pattern not found> message. So it appears
that the command reported to be bound to that key is not invoked at
all.
next reply other threads:[~2006-07-19 14:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 14:03 Ilya N. Golubev [this message]
2006-07-20 17:04 ` dispatched randomly [key bindings reported incorrectly] Ilya N. Golubev
2006-07-20 22:16 ` Kevin Rodgers
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=278xmpite8.fsf@mo.msk.ru \
--to=gin@mo.msk.ru \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).