GNU bug report logs - #60190
29.0.50; Improve `Info-goto-node-web'

Previous Next

Full log

View this message in rfc822 format

From: Eduardo Ochs <eduardoochs <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 60190 <at> debbugs.gnu.org, mbork <at> mbork.pl, Stefan Kangas <stefankangas <at> gmail.com>
Subject: bug#60190: 29.0.50; Improve `Info-goto-node-web'
Date: Tue, 20 Dec 2022 12:20:41 -0300

On Tue, 20 Dec 2022 at 11:02, Eli Zaretskii <eliz <at> gnu.org> wrote:
>
> > From: Stefan Kangas <stefankangas <at> gmail.com>
> > Date: Mon, 19 Dec 2022 22:44:41 -0600
> > Cc: 60190 <at> debbugs.gnu.org, mbork <at> mbork.pl
> >
> > Eli Zaretskii <eliz <at> 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.

How would that work for packages that are in MELPA? Some of them have
Info manuals that can be accessed on the web, but that are in
random(ish) places...

  Cheers,
    Eduardo Ochs
    http://angg.twu.net/eepitch.html

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.