From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 60190@debbugs.gnu.org, mbork@mbork.pl, eduardoochs@gmail.com
Subject: bug#60190: 29.0.50; Improve `Info-goto-node-web'
Date: Tue, 20 Dec 2022 16:02:13 +0200 [thread overview]
Message-ID: <83edsucgwq.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkcesxd4MMv3_=FmVmHpqvUJ74Ck6hpT3XEasvm2Eiw6g@mail.gmail.com> (message from Stefan Kangas on Mon, 19 Dec 2022 22:44:41 -0600)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Mon, 19 Dec 2022 22:44:41 -0600
> Cc: 60190@debbugs.gnu.org, mbork@mbork.pl
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I'm not against the table, I'm saying that for the manuals that come
> > with Emacs we don't need any entries in the table. IOW, the table
> > could be provided, but only for extensions by users, if they want to
> > extend this to manuals which don't come as part of the Emacs
> > distribution.
>
> I think we should include a list of built-in manuals, so that we only
> send users to known-good places, and tell them otherwise. The drawback
> is that we need to remember to update the list when we add a new manual.
There's no need to maintain a list, we can produce it at build time by
looking at the DIR file we produce in the info subdirectory. This
would solve the maintenance problem cleanly and easily.
next prev parent reply other threads:[~2022-12-20 14:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 6:23 bug#60190: 29.0.50; Improve `Info-goto-node-web' Marcin Borkowski
2022-12-19 7:02 ` Eduardo Ochs
2022-12-19 12:31 ` Eli Zaretskii
2022-12-19 15:05 ` Eduardo Ochs
2022-12-19 15:27 ` Eli Zaretskii
2022-12-20 4:44 ` Stefan Kangas
2022-12-20 14:02 ` Eli Zaretskii [this message]
2022-12-20 15:20 ` Eduardo Ochs
2022-12-20 15:33 ` Eli Zaretskii
2022-12-21 1:05 ` Stefan Kangas
2022-12-21 12:04 ` Eli Zaretskii
2022-12-19 17:23 ` Drew Adams
2022-12-19 19:24 ` Marcin Borkowski
2022-12-19 20:33 ` Drew Adams
2022-12-20 6:00 ` Marcin Borkowski
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=83edsucgwq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60190@debbugs.gnu.org \
--cc=eduardoochs@gmail.com \
--cc=mbork@mbork.pl \
--cc=stefankangas@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).