From: Stefan Kangas <stefan@marxist.se>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 8947@debbugs.gnu.org
Subject: bug#8947: 24.0.50; `describe-mode': `help-mode-map' pollutes minor mode descriptions
Date: Thu, 21 Oct 2021 12:44:23 -0700 [thread overview]
Message-ID: <CADwFkmm9oDOiBCWvjqseFfqBhF07kSdKUHRmeWT-WmrZ9ZthHw@mail.gmail.com> (raw)
In-Reply-To: <87y47tbke1.fsf@web.de> (Michael Heerdegen's message of "Sun, 01 May 2016 22:20:22 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Drew Adams <drew.adams@oracle.com> writes:
>
>> The recipe I gave was this:
>>
>> emacs -Q
>>
>> Visit any *.el file, hit `C-h m', then search for `Transient'
>> ^^^^^^^^^^^^^^^^^^^
>> in *Help*. The help for `transient-mark-mode' says this:
>>
>> "...for example, incremental search, <, and >."
>>
>> And I explained the cause: The doc for `transient-mark-mode'
>> is being picked up after *Help* has become the current buffer.
>> That is not the correct behavior.
>
> I agree. I can reproduce this, and your explanation makes sense.
I can no longer reproduce this using the above recipe; the
`transient-mode-mark' docstring was changed in commit b99192fe24fc.
Do we have an up-to-date reproducer for this?
next prev parent reply other threads:[~2021-10-21 19:44 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
2016-05-01 20:06 ` Drew Adams
2016-05-01 20:20 ` Michael Heerdegen
2021-10-21 19:44 ` Stefan Kangas [this message]
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=CADwFkmm9oDOiBCWvjqseFfqBhF07kSdKUHRmeWT-WmrZ9ZthHw@mail.gmail.com \
--to=stefan@marxist.se \
--cc=8947@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/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).