From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 8947@debbugs.gnu.org
Subject: bug#8947: 24.0.50; `describe-mode': `help-mode-map' pollutes minor mode descriptions
Date: Sun, 01 May 2016 20:32:00 +0200 [thread overview]
Message-ID: <8760uxzl27.fsf@gnus.org> (raw)
In-Reply-To: <878tzyouz0.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 28 Apr 2016 13:04:19 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Here's a shorter test case:
>
> (progn
> (describe-function 'transient-mark-mode)
> (with-current-buffer (get-buffer "*Help*")
> (revert-buffer)))
>
> After answering "y", the `M-'s will go missing before the `<' and '>'.
Hm... well, after fiddling with this a bit more, I see that it's
describing all these minor mode bindings in the context of the buffer
you were in when you called the description command. I think that's
correct. If you have these commands bound to `<' etc in that mode, then
that is what the help command will say.
So the form above will give different results when run from, say,
*scratch* and from a special mode, and that's fine. Closing.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-05-01 18:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 22:41 bug#8947: 24.0.50; `describe-mode': `help-mode-map' pollutes minor mode descriptions Drew Adams
2014-02-10 5:07 ` Lars Ingebrigtsen
2016-04-28 11:04 ` Lars Ingebrigtsen
2016-05-01 18:32 ` Lars Ingebrigtsen [this message]
2016-05-01 20:06 ` Drew Adams
2016-05-01 20:20 ` Michael Heerdegen
2021-10-21 19:44 ` Stefan Kangas
2021-10-21 20:59 ` bug#8947: [External] : " Drew Adams
2021-10-21 21:19 ` Stefan Kangas
2021-10-21 21:48 ` Drew Adams
2021-10-21 22:21 ` Stefan Kangas
2016-05-01 20:23 ` Lars Ingebrigtsen
2016-10-21 14:30 ` Drew Adams
2016-10-21 14:51 ` Noam Postavsky
2016-10-21 15:42 ` Drew Adams
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=8760uxzl27.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=8947@debbugs.gnu.org \
--cc=drew.adams@oracle.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 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).