From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 44149@debbugs.gnu.org, Jean Louis <bugs@gnu.support>
Subject: bug#44149: 28.0.50; M-x finder-by-keyword, giving weird descriptions for gnus and org
Date: Mon, 26 Oct 2020 16:29:34 -0400 [thread overview]
Message-ID: <jwvtuugoi2d.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CADwFkmm_G0SLYqQApnzroJGm4jpr3-igNTZ1LrsAbpeR1Ywzxg@mail.gmail.com> (Stefan Kangas's message of "Thu, 22 Oct 2020 12:17:28 -0700")
>> Just tell me if it is a joke that gnus is described this way.
>> gnus 5.13 built-in Identifying spam
> The description comes from spam.el:
> ./spam.el:1:;;; spam.el --- Identifying spam
But why is it put under the name "gnus"?
>> Another issue, Org is described as:
>> org 9.3 built-in Export Framework for Org Mode
> This description comes from ox.el
> ./ox.el:1:;;; ox.el --- Export Framework for Org Mode [...]
Similarly, why is it put under the name "org"?
> commit 851535f58745dcfbc8798b3a34b4fea852f93a3e
> Author: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Sat Jul 6 18:42:02 2019 -0400
>
> * lisp/emacs-lisp/nadvice.el: Make it a package separate from `emacs`.
>
> * lisp/finder.el (finder-compile-keywords): Grab version from
> package--builtin-versions when available.
>
> It makes "(or (eq base-name package) version)" below that always be true,
I don't understand why it does that.
> Reverting the above commit fixes this issue here.
I get the impression that there's some other underlying problem.
> I'm not sure how best to fix this without breaking something else.
> Perhaps Stefan M has an idea?
I don't understand this code enough to give much guidance, I'm afraid.
Stefan
next prev parent reply other threads:[~2020-10-26 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 17:24 bug#44149: 28.0.50; M-x finder-by-keyword, giving weird descriptions for gnus and org Jean Louis
2020-10-22 19:17 ` Stefan Kangas
2020-10-26 20:29 ` Stefan Monnier [this message]
2020-10-27 1:19 ` Stefan Kangas
2020-10-27 18:39 ` Stefan Monnier
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=jwvtuugoi2d.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=44149@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=stefankangas@gmail.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).