all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: auto-update of Info dir file?
Date: Tue, 16 May 2006 10:54:09 -0700	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICAECODGAA.drew.adams@oracle.com> (raw)
In-Reply-To: <uves53m8b.fsf@gnu.org>

    I think we could solve the problem much easier: if the user wants a
    manual called "mumble",

What do you mean here by "the user wants"? Are you speaking of the user who
executes Emacs command `info' or the user (perhaps a sysadmin or programmer,
not necessarily the end-user of Emacs) who adds the Info files to the
directory?

The end user might not know that s?he wants a particular manual. If the
manual doesn't appear in the Info list (catch-22), then the user might not
even be aware that the manual exists. The idea was to have invocation of
Emacs command `info' populate Info with all available manuals, without the
end user needing to know anything about what they are.

Also, how will Emacs tell what "the user wants" in this context? Even if the
end user does know that s?he wants a particular manual (and that it should
be available), how is that communicated to Emacs in your scenario?

    and there's no such entry in DIR, look for a
    _file_ called `mumble' with several possible extensions.  This is what
    the stand-alone Info does, so adding this to Emacs will increase
    compatibility between the two readers.  Doing this bears no run-time
    penalty, and almost the same benefits for the user.

I think this should be push rather than pull. That is, populating Info
should not be demand-driven by the user; it should be done automatically,
based on all available Info files. It can be demand-driven in terms of
_when_ it happens (dynamically, when the user invokes Emacs command `info'
for the first time in a session), but not in terms of _which_ manuals end up
populating the `dir' file.

  reply	other threads:[~2006-05-16 17:54 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=DNEMKBNJBGPAOPIJOOICAECODGAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.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.