unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eduardo Ochs <eduardoochs@gmail.com>
Cc: 60190@debbugs.gnu.org, mbork@mbork.pl
Subject: bug#60190: 29.0.50; Improve `Info-goto-node-web'
Date: Mon, 19 Dec 2022 17:27:42 +0200	[thread overview]
Message-ID: <83359be7m9.fsf@gnu.org> (raw)
In-Reply-To: <CADs++6gFBSOdjEN284ybzvWbzZBh4u2PnR2z8SWY5PTLgUGNLQ@mail.gmail.com> (message from Eduardo Ochs on Mon, 19 Dec 2022 12:05:53 -0300)

> From: Eduardo Ochs <eduardoochs@gmail.com>
> Date: Mon, 19 Dec 2022 12:05:53 -0300
> Cc: mbork@mbork.pl, 60190@debbugs.gnu.org
> 
> On Mon, 19 Dec 2022 at 09:31, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > > Cc: 60190@debbugs.gnu.org
> > > From: Eduardo Ochs <eduardoochs@gmail.com>
> > > Date: Mon, 19 Dec 2022 04:02:47 -0300
> > >
> > >   (defvar Info-url-base
> > >     '(("emacs"  . "http://www.gnu.org/software/emacs/manual/html_node/emacs/")
> > >       ("elisp"  . "http://www.gnu.org/software/emacs/manual/html_node/elisp/")
> > >       ("eintr"  .
> > > "http://www.gnu.org/software/emacs/emacs-lisp-intro/html_node/")
> > >       ("efaq"   . "https://www.gnu.org/software/emacs/manual/html_node/efaq/")
> > >       ("cl"     . "http://www.gnu.org/software/emacs/manual/html_node/cl/")
> > >       ("eshell" . "https://www.gnu.org/software/emacs/manual/html_node/eshell/")
> > >       ("org"    . "http://www.gnu.org/software/emacs/manual/html_node/org/")))
> >
> > Aren't these mappings trivial?  You seem to be prepending the same
> > prefix to the exact name of the Info file (sans extension).  Or what
> > did I miss?
> 
> No, look at the case of the eintr...

Why is that necessary?  If you go to this page:

  https://www.gnu.org/software/emacs/manual/

you will see there a link to eintr which is this:

  https://www.gnu.org/software/emacs/manual/eintr.html

And if you follow it, you will find the manual itself at this URL:

  https://www.gnu.org/software/emacs/manual/html_node/eintr/index.html

which AFAIU doesn't require any database to generate.  Right?

> And if we use a table for the conversion then users can add new
> entries to it easily, including entries that don't follow that
> pattern.

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.





  reply	other threads:[~2022-12-19 15:27 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 [this message]
2022-12-20  4:44         ` Stefan Kangas
2022-12-20 14:02           ` Eli Zaretskii
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=83359be7m9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60190@debbugs.gnu.org \
    --cc=eduardoochs@gmail.com \
    --cc=mbork@mbork.pl \
    /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).