From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 42753@debbugs.gnu.org
Subject: bug#42753: 26.3; `info-lookup.el': Add all manuals delivered by `emacs -Q', for `emacs-lisp-mode'
Date: Fri, 08 Oct 2021 18:23:38 +0200 [thread overview]
Message-ID: <878rz332ph.fsf@gmx.de> (raw)
In-Reply-To: <83pmsfy023.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 08 Oct 2021 19:05:08 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
Hi Eli,
>> They are integrated in the Emacs source tree, so we could negotiate with
>> the maintainers. Even if we cannot change all manuals this way, the
>> number of exceptions in info-lookup would decrease.
>
> I meant the likes of Python manual, the glibc manual, and others.
> Good luck negotiating with them. And then there's always a
> possibility that the user will want to add some manual we know nothing
> about.
My reply was about Emacs integrated manuals.
> I think a better solution will be to be tolerant, i.e. look for nodes
> that contain "index", and maybe also "function" or "variable", in them
> regardless of the rest.
Sure. Same for *ELPA manuals. But I believe we also should use some
conventions for manuals under our control.
Best regards, Michael.
next prev parent reply other threads:[~2021-10-08 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<d69397a7-acf7-4803-9cba-f7e0686712f4@default>
[not found] ` <<835z9t7cme.fsf@gnu.org>
2020-08-08 14:28 ` bug#42753: 26.3; `info-lookup.el': Add all manuals delivered by `emacs -Q', for `emacs-lisp-mode' Drew Adams
2020-08-15 14:22 ` Michael Albinus
2021-08-29 22:10 ` Lars Ingebrigtsen
2021-10-08 13:36 ` Lars Ingebrigtsen
2021-10-08 14:02 ` Eli Zaretskii
2021-10-08 14:33 ` Michael Albinus
2021-10-08 16:05 ` Eli Zaretskii
2021-10-08 16:23 ` Michael Albinus [this message]
2021-10-08 17:36 ` Eli Zaretskii
2021-10-09 11:17 ` Lars Ingebrigtsen
2021-10-09 12:45 ` Lars Ingebrigtsen
2020-08-07 22:20 Drew Adams
2020-08-08 8:42 ` Eli Zaretskii
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=878rz332ph.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=42753@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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.