From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: hmelman@gmail.com, alan@idiocy.org, 54961@debbugs.gnu.org,
larsi@gnus.org, juri@linkov.net
Subject: bug#54961: 28.1; info-display-manual completions issues
Date: Wed, 20 Apr 2022 15:38:01 +0300 [thread overview]
Message-ID: <8335i8szfa.fsf@gnu.org> (raw)
In-Reply-To: <jwvilr4uftn.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 20 Apr 2022 08:00:02 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: hmelman@gmail.com, alan@idiocy.org, juri@linkov.net, larsi@gnus.org,
> 54961@debbugs.gnu.org
> Date: Wed, 20 Apr 2022 08:00:02 -0400
>
> > Yes, in a function deceptively named Info-dir-remove-duplicates.
>
> IIRC I'm the one to blame for that code, and my memory is fuzzy but
> I seem to remember that the case I wanted to fix was one where there
> were indeed several entries by the same name, which might explain why
> I ended up naming it that way, although in retrospect it probably wasn't
> the best choice ;-)
That function does remove duplicates. The problem is that it also
rearranges entries of the same section to bring them together, and
that part is not reflected in its name at all. And since the function
doesn't have a doc string, it's impossible to guess that it does this
second part, except by reading the code.
next prev parent reply other threads:[~2022-04-20 12:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 19:04 bug#54961: 28.1; info-display-manual completions issues Howard Melman
2022-04-16 9:39 ` Lars Ingebrigtsen
2022-04-16 11:27 ` Howard Melman
2022-04-16 14:00 ` Lars Ingebrigtsen
2022-04-16 14:38 ` Lars Ingebrigtsen
2022-04-16 15:21 ` Howard Melman
2022-04-16 15:23 ` Lars Ingebrigtsen
2022-04-18 19:02 ` Juri Linkov
2022-04-18 19:45 ` Howard Melman
2022-04-18 21:28 ` Howard Melman
2022-04-19 5:35 ` Eli Zaretskii
2022-04-19 13:27 ` Howard Melman
2022-04-19 16:55 ` Eli Zaretskii
2022-04-19 18:43 ` Howard Melman
2022-04-19 18:55 ` Eli Zaretskii
2022-04-19 19:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-20 5:39 ` Eli Zaretskii
2022-04-20 12:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-20 12:38 ` Eli Zaretskii [this message]
2022-04-19 19:07 ` Howard Melman
2022-04-19 19:24 ` Eli Zaretskii
2022-04-19 19:24 ` Juri Linkov
2022-04-20 17:01 ` Alan Third
2022-04-20 19:10 ` Howard Melman
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=8335i8szfa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54961@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=hmelman@gmail.com \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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).