From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 72787@debbugs.gnu.org, me@eshelyaron.com,
Pip Cet <pipcet@protonmail.com>
Subject: bug#72787: 31.0.50; Invalid describe-function completion candidates
Date: Sun, 25 Aug 2024 22:37:01 -0400 [thread overview]
Message-ID: <jwv8qwk9fnb.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87o75gvz5l.fsf@web.de> (Michael Heerdegen's message of "Mon, 26 Aug 2024 03:41:26 +0200")
>> This appears to be caused by commit
>> 45ae4de0e7ce99c88c62f940f605bca693b8e33f:
>>
>> * lisp/help-fns.el (help-definition-prefixes): Don't delete the hashtable
> Stefan's commit indeed seems related. Stefan, could you maybe
> have a look please?
I think this report makes it clear that
45ae4de0e7ce99c88c62f940f605bca693b8e33f should not have gone to
`emacs-30` but to `master`. AFAIK it did not fix a regression or even
a user-visible bug.
Stefan
next prev parent reply other threads:[~2024-08-26 2:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 10:54 bug#72787: 31.0.50; Invalid describe-function completion candidates Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-24 11:15 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-26 1:41 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-26 2:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-08-26 23:57 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-31 9:54 ` Eli Zaretskii
2024-09-01 17:41 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-01 18:00 ` Eli Zaretskii
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=jwv8qwk9fnb.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=72787@debbugs.gnu.org \
--cc=me@eshelyaron.com \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
--cc=pipcet@protonmail.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.