unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Howard Melman <hmelman@gmail.com>
Cc: 54961@debbugs.gnu.org
Subject: bug#54961: 28.1; info-display-manual completions issues
Date: Sat, 16 Apr 2022 16:38:33 +0200	[thread overview]
Message-ID: <87wnfpccuu.fsf@gnus.org> (raw)
In-Reply-To: <C20CB691-DB53-4C05-B7A5-1B0053C07037@gmail.com> (Howard Melman's message of "Fri, 15 Apr 2022 15:04:42 -0400")

Howard Melman <hmelman@gmail.com> writes:

> First, they include manuals named "./" and "../" which
> shouldn't be there.
>
> Second I seem to see duplicates, if I complete with input
> "emacs" I see candidates "emacs" and "emacs.info.gz" and
> similar duplicates for emacs-mime and emacs-gnutls, so 3
> candidates show as 6.  This may be an artifact of the
> macport build I'm using.  It happens from emacs -q and I
> can't easily test on vanilla gnu emacs.

I've now fixed this in Emacs 29.

> Third it would be really nice if there were an
> affixation-function that added the one line description of
> the manual for a completions framework to show when
> completions-detailed is t.  Perhaps it could get the info
> from Info-dir-contents?

But I'm not sure how to fix this in a scalable way.  Info-dir-contents
may not exist, and may include fewer info files than what we want to
have in this prompt, I think?  And as previously noted, I think it'd
just be too slow to look in every file (I've got 133 files now, down
from 300 before filtering duplicates)..

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2022-04-16 14: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 [this message]
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
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=87wnfpccuu.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=54961@debbugs.gnu.org \
    --cc=hmelman@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).