From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 16407@debbugs.gnu.org
Subject: bug#16407: Info-directory-list should always put this Emacs's info direc first
Date: Fri, 10 Jan 2014 09:16:26 +0200 [thread overview]
Message-ID: <838uuocnn9.fsf@gnu.org> (raw)
In-Reply-To: <d038kwjsn4.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Date: Fri, 10 Jan 2014 00:46:39 -0500
>
> Therefore, the directory of Info files that come with Emacs normally
> should come last (so that local files override standard ones), unless
> Emacs is installed into a non-standard directory. In the latter case,
> the directory of Info files that come with Emacs should be first in
> this list.
>
> I don't think this logic makes sense any more. I think the directory of
> Info files that come with Emacs should *always* be placed at the front of
> the result (even before INFOPATH entries).
That leaves system administrators no means of forcing a specific
version of Info manual to be found by default. With INFOPATH taking
precedence, they can.
Also, Emacs comes with a few manuals that can have other versions from
elsewhere (like info.info or gnus.info).
> I assume the current logic dates from a time when it was thought likely
> that a site might want to customize the Emacs info pages. I don't think
> this happens any more. What I think does happen is people having
> multiple versions of Emacs installed.
Is this the only situation where the current arrangement doesn't DTRT,
or are there more? If this is the only one, then you cannot solve it
successfully: the Info system simply doesn't support well the use case
where several different manuals have identical names. The only way to
have the correct results is either by "C-u C-h i" and point Emacs to
the specific file name, or run all but one version uninstalled.
> In this case, I think Emacs version N should always display the info
> pages associated with version N. So Emacs should always put its own
> info directory first.
What if the user installs newer versions of, say, Gnus or Org from
their respective repositories?
next prev parent reply other threads:[~2014-01-10 7:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 5:46 bug#16407: Info-directory-list should always put this Emacs's info direc first Glenn Morris
2014-01-10 7:16 ` Eli Zaretskii [this message]
2014-01-10 7:38 ` Glenn Morris
2014-01-10 7:44 ` Glenn Morris
2014-01-10 7:50 ` Glenn Morris
2014-01-10 8:07 ` Eli Zaretskii
2014-01-10 20:03 ` Glenn Morris
2014-01-10 8:09 ` Eli Zaretskii
2014-01-10 20:05 ` Glenn Morris
2014-01-10 20:20 ` Eli Zaretskii
2014-01-10 8:05 ` Glenn Morris
2014-01-10 8:21 ` Eli Zaretskii
2014-01-10 15:03 ` Stefan Monnier
2014-01-10 15:16 ` Eli Zaretskii
2014-01-10 16:36 ` Rüdiger Sonderfeld
2014-01-10 8:19 ` Eli Zaretskii
2014-01-10 20:11 ` Glenn Morris
2014-01-10 20:36 ` Eli Zaretskii
2014-01-10 21:03 ` Glenn Morris
2014-01-10 23:21 ` Glenn Morris
2014-01-10 20:54 ` Stefan Monnier
2014-01-10 19:47 ` Achim Gratz
2022-04-23 14:28 ` Lars Ingebrigtsen
2022-05-22 11:33 ` Lars Ingebrigtsen
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=838uuocnn9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16407@debbugs.gnu.org \
--cc=rgm@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).