From: Michael Lee <michael.saelee@gmail.com>
Subject: viper-want-ctl-h-help broken?
Date: Sun, 08 May 2005 03:24:31 GMT [thread overview]
Message-ID: <2005050722243116807%michaelsaelee@gmailcom> (raw)
I recently upgraded to gnu emacs 22.0.50.1 (compiled for darwin/os x)
and discovered that binding C-h to help-command (or just setting
viper-want-ctl-h-help to true) doesn't work any longer for help queries
of type C-h k (for getting keystroke help). This happens when I'm in
viper mode, irrespective of whether I'm actually in viper editing mode
or have switched temporarily to emacs-mode (C-z). I keep getting the
error message "Wrong type argument: arrayp, nil" when I try to lookup
any keystroke. If I turn off viper mode with viper-go-away, C-h k
resumes working properly.
Can anyone help to figure out how to fix this, or what I might have
wrong in my configuration?
Thanks!
Michael
next reply other threads:[~2005-05-08 3:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-08 3:24 Michael Lee [this message]
2005-05-09 21:20 ` viper-want-ctl-h-help broken? Edward O'Connor
[not found] <mailman.4303.1115674444.2819.help-gnu-emacs@gnu.org>
2005-05-10 2:22 ` Michael Lee
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=2005050722243116807%michaelsaelee@gmailcom \
--to=michael.saelee@gmail.com \
/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.
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).