From: Howard Melman <hmelman@gmail.com>
To: 54961@debbugs.gnu.org
Subject: bug#54961: 28.1; info-display-manual completions issues
Date: Fri, 15 Apr 2022 15:04:42 -0400 [thread overview]
Message-ID: <C20CB691-DB53-4C05-B7A5-1B0053C07037@gmail.com> (raw)
I'm happy to see info-display-manual added to Emacs 28.1 but
the completions offered leave something to be desired.
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.
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?
Howard
In GNU Emacs 28.1 (build 1, x86_64-apple-darwin20.6.0, Carbon Version 164 AppKit 2022.6)
of 2022-04-09 built on Mac-1649520554451.local
Repository revision: ee79b048bbb2fd4a962dfb2204cc7a2f0d5237d8
Repository branch: 28.1-mac-9.0-CI
Windowing system distributor 'Apple Inc.', version 11.6.5
System Description: macOS 11.6.5
Configured using:
'configure --with-mac
--enable-locallisppath=/usr/local/share/emacs/site-lisp:/opt/homebrew/share/emacs/site-lisp
--enable-mac-app=/Users/runner/work/homebrew-emacsmacport/homebrew-emacsmacport/build-scripts/emacs-source/tmproot
--prefix=/Users/runner/work/homebrew-emacsmacport/homebrew-emacsmacport/build-scripts/emacs-source/tmproot
--enable-mac-self-contained --with-modules'
next reply other threads:[~2022-04-15 19:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 19:04 Howard Melman [this message]
2022-04-16 9:39 ` bug#54961: 28.1; info-display-manual completions issues 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C20CB691-DB53-4C05-B7A5-1B0053C07037@gmail.com \
--to=hmelman@gmail.com \
--cc=54961@debbugs.gnu.org \
/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.