From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@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 15:11:45 -0500 [thread overview]
Message-ID: <r738kviola.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <8338kwckqh.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Jan 2014 10:19:18 +0200")
Eli Zaretskii wrote:
> On a multi-user system, INFOPATH can be customized differently for
> each user, but /usr/share/info is a single directory. Suppose some
> users want to stay with an older Emacs, while others want the bleeding
> edge.
I don't really get your point. I contend that "Emacs N should show the
manuals for version N", without the user needing to do anything special.
(I'm assuming throughout that each Emacs version is installed in a
separate location, otherwise the info pages stomp all over each other
anyway, as you said.)
For example:
As a user, I have a local software directory /home/me/software, where I
install things. So I have INFOPATH=/home/me/software/info: in my
environment. There is Emacs version N in there. I have other Emacs
versions installed in other places, which I want to use at times. All of
them end up finding the info pages from Emacs version N.
> Experience has taught us that there are too many "fringe cases" when
> Info docs are concerned. The code to which you pointed was a result
> of prolonged discussions in the past, and many micro-corrections due
> to these fringe cases.
Sorry, I think it's overly complicated for this day-and-age, and could
stand to be simplified.
>> And note that the Mac platform has already behaved as I request for some
>> years. I don't recall seeing any complaints.
>
> This goes both ways: I don't recall complaints about the current
> arrangement, either.
It's me, I'm the complainer! :)
Anyway, my one sentence summary is that it just seems crazy to me that
Emacs does not reliably find its own info pages.
next prev parent reply other threads:[~2014-01-10 20:11 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
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 [this message]
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=r738kviola.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=16407@debbugs.gnu.org \
--cc=eliz@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).