all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Wed, 21 Dec 2022 14:04:01 +0200	[thread overview]
Message-ID: <83fsd9arpq.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmk=Xk6NftrcD4x_LXjDKo4U6tkupqztzhK0VcKjpbyuww@mail.gmail.com> (message from Stefan Kangas on Tue, 20 Dec 2022 19:05:01 -0600)

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Tue, 20 Dec 2022 19:05:01 -0600
> Cc: eduardoochs@gmail.com, 60190@debbugs.gnu.org, mbork@mbork.pl
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > 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.
> 
> OK, we could do that.
> 
> What would be the cleanest way to make that information available to
> Lisp?  Do we just generate a new file at build-time and put it there, or
> is there a better way?

I'd think we could generate a info-something.eld file that would then
be installed by "make install" and read by info.el when this command
is invoked.  WDYT?





  reply	other threads:[~2022-12-21 12:04 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83fsd9arpq.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 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.