From: Richard Stallman <rms@gnu.org>
To: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: [lennart.borgman@gmail.com: C-h k does not catch text properies keymaps]
Date: Tue, 06 Mar 2007 11:01:35 -0500 [thread overview]
Message-ID: <E1HOc6Z-0007kC-S0@fencepost.gnu.org> (raw)
In-Reply-To: <45EC8CB5.60307@gmail.com> (lennart.borgman@gmail.com)
Ok, thanks. I can see it is partly correct and useful. But the
information about the other function, should not that be shown too?
There is no way to enter just an up-event as argument to C-h k. So,
in the case where the down-event has a binding, there is no way to ask
about the up-event's binding.
Since the up-event will always follow the down-event in practice, it
would be useful for C-h k to mention that the up-event has a binding
too. That would be more convenient and natural than implementing
a separate way to ask for the up-event.
next prev parent reply other threads:[~2007-03-06 16:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 2:56 [lennart.borgman@gmail.com: C-h k does not catch text properies keymaps] Richard Stallman
2007-03-05 15:27 ` Chong Yidong
2007-03-05 21:21 ` David Kastrup
2007-03-05 21:33 ` Lennart Borgman (gmail)
2007-03-05 22:11 ` Chong Yidong
2007-03-05 22:35 ` Lennart Borgman (gmail)
2007-03-05 22:38 ` Chong Yidong
2007-03-05 23:30 ` Lennart Borgman (gmail)
2007-03-06 22:36 ` Richard Stallman
2007-03-06 22:48 ` Lennart Borgman (gmail)
2007-03-07 9:10 ` Richard Stallman
2007-03-07 12:01 ` Lennart Borgman (gmail)
2007-03-17 20:32 ` Viper doesn't properly handle C-h k for mouse clicks Chong Yidong
2007-03-21 16:19 ` Chong Yidong
2007-03-21 17:01 ` Michael Kifer
2007-03-06 16:01 ` Richard Stallman [this message]
2007-03-06 17:25 ` [lennart.borgman@gmail.com: C-h k does not catch text properies keymaps] Lennart Borgman (gmail)
2007-03-05 21:50 ` Richard Stallman
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=E1HOc6Z-0007kC-S0@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.