From: Juri Linkov <juri@linkov.net>
To: Howard Melman <hmelman@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 54961@debbugs.gnu.org
Subject: bug#54961: 28.1; info-display-manual completions issues
Date: Mon, 18 Apr 2022 22:02:55 +0300 [thread overview]
Message-ID: <868rs2tm4w.fsf@mail.linkov.net> (raw)
In-Reply-To: <08B1B8C9-F276-4B4A-BC41-8719124A5C9A@gmail.com> (Howard Melman's message of "Sat, 16 Apr 2022 11:21:31 -0400")
> I'm also frustrated that packages I install put their manuals at the top,
> above Emacs and Elisp which are my most referenced manuals.
> I thought there was a bug about this, but I couldn't find it. There
> are several others about duplicates in the dir dealing with the
> complexities of finding multiple versions of a manual in the info paths.
The problem is that authors of these packages are using
@dircategory Emacs
instead of the correct
@dircategory Emacs misc features
that would put their manuals below Emacs and Elisp.
next prev parent reply other threads:[~2022-04-18 19:02 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 [this message]
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=868rs2tm4w.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=54961@debbugs.gnu.org \
--cc=hmelman@gmail.com \
--cc=larsi@gnus.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.