From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: auto-update of Info dir file?
Date: Mon, 15 May 2006 23:31:20 +0300 [thread overview]
Message-ID: <u3bfb3u93.fsf@gnu.org> (raw)
In-Reply-To: <MEEKKIABFKKDFJMPIOEBMEHGDBAA.drew.adams@oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Mon, 15 May 2006 08:28:50 -0700
>
> For each directory in `Info-directory-list', for each top-level file in the
> directory (i.e. whose name doesn't end in "-N", N=1,2,3...): Check if there
> is a corresponding entry in the Info `dir' file (in
> `Info-dir-contents-directory'), and, if not, add one.
I think this will slow down Info startup to an intolerable degree.
For example, I have more than 70 such top-level Info files in my Info
directory, some of them compressed.
> Perhaps there is already part of the mechanism for doing this. When I look
> in some Info files now I see (START|END)-INFO-DIR-ENTRY, which makes me
> think there must already be a means of adding the entry. Perhaps all that's
> missing is to have `info' do that on the fly automatically for each
> top-level Info file in the directories of `Info-directory-list'.
When a package is installed, its "make install" target should
automatically run the install-info program, which updates the menu in
DIR. So, for systems that are well set up, this problem does not
exist, and I don't see why we should punish users of such systems on
behalf of the other kind.
> I mention this because of a question in help-gnu-emacs today and a reply
> advising the user to add the entry to the `dir' file.
That user got half the world and their dog mixed up. I wouldn't
recommend jumping to conclusions based on that case alone.
> If this were costly in performance, it might be done only on first use of
> `info' in a session.
It will be still painful, IMO.
next prev parent reply other threads:[~2006-05-15 20:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 15:28 auto-update of Info dir file? Drew Adams
2006-05-15 15:39 ` Andreas Schwab
2006-05-15 15:53 ` Drew Adams
2006-05-15 16:54 ` Andreas Schwab
2006-05-15 20:31 ` Eli Zaretskii [this message]
2006-05-16 3:54 ` Stefan Monnier
2006-05-16 4:17 ` Miles Bader
2006-05-16 6:00 ` David Kastrup
2006-05-16 17:39 ` Eli Zaretskii
2006-05-17 2:24 ` Miles Bader
2006-05-16 17:36 ` Eli Zaretskii
2006-05-16 17:54 ` Drew Adams
2006-05-16 18:14 ` Eli Zaretskii
2006-05-16 19:33 ` Drew Adams
2006-05-17 3:24 ` Eli Zaretskii
2006-05-16 19:44 ` Richard Stallman
2006-05-16 18:44 ` Stefan Monnier
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=u3bfb3u93.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.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 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).