From: jidanni@jidanni.org
To: bug-gnu-emacs@gnu.org
Cc: ding@gnus.org
Subject: describe-bindings does not list text properties and overlay bindings!
Date: Sun, 03 Apr 2011 09:04:40 +0800 [thread overview]
Message-ID: <877hbctaaf.fsf_-_@jidanni.org> (raw)
In-Reply-To: <m37hbc8k6w.fsf@quimbies.gnus.org>
Dear Emacs Professionals/Nurds,
Since back in the 1980's I've depended on C-h b to tell me what all the
keys are currently bound to in the buffer I'm in.
I even printed them out on paper and studied them all.
C-h b runs the command describe-bindings, which is an interactive
compiled Lisp function in `help.el'.
Show a list of all defined keys, and their definitions.
We put that list in a buffer, and display the buffer.
So you can understand my shock upon finding out,
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
LMI> jidanni@jidanni.org writes:
>> Why when in the article buffer C-h k { says
>> } runs the command w3m-next-image, which is an interactive compiled
>> but C-h b does not list it?
LMI> `C-h b' just lists the keys in the current mode(s) of the buffer. It
LMI> doesn't list the keys that are bound due to text properties and
LMI> overlays. It probably should, and that's an Emacs bug.
OK, I'll hereby report it.
next prev parent reply other threads:[~2011-04-03 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 12:56 why doesn't C-h b list w3m keys jidanni
2011-04-02 20:36 ` Lars Magne Ingebrigtsen
2011-04-03 1:04 ` jidanni [this message]
2019-08-21 21:05 ` bug#8414: describe-bindings does not list text properties and overlay bindings! Lars Ingebrigtsen
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=877hbctaaf.fsf_-_@jidanni.org \
--to=jidanni@jidanni.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=ding@gnus.org \
/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 NNTP newsgroup(s).