From: Lars Ingebrigtsen <larsi@gnus.org>
To: jidanni@jidanni.org
Cc: 8414@debbugs.gnu.org, ding@gnus.org
Subject: Re: bug#8414: describe-bindings does not list text properties and overlay bindings!
Date: Wed, 21 Aug 2019 14:05:36 -0700 [thread overview]
Message-ID: <87sgpuw7of.fsf@mouse.gnus.org> (raw)
In-Reply-To: <877hbctaaf.fsf_-_@jidanni.org> (jidanni@jidanni.org's message of "Sun, 03 Apr 2011 09:04:40 +0800")
jidanni@jidanni.org writes:
> 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.
(I'm going through old bug reports that have unfortunately gotten no
attention yet.)
I had a peek at this now -- I hit `C-h b' on text that has a `keymap'
property, and it looks like it's been fixed in the intervening years:
`keymap' Property Bindings:
key binding
--- -------
TAB shr-next-link
RET eww-follow-link
ESC Prefix Command
+ image-increase-size
- image-decrease-size
So I'm closing this bug report. If you're still seeing this, please
reopen.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-08-21 21:05 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 ` describe-bindings does not list text properties and overlay bindings! jidanni
2019-08-21 21:05 ` Lars Ingebrigtsen [this message]
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=87sgpuw7of.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=8414@debbugs.gnu.org \
--cc=ding@gnus.org \
--cc=jidanni@jidanni.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).