unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 22:36:21 +0200	[thread overview]
Message-ID: <838uunbmm2.fsf@gnu.org> (raw)
In-Reply-To: <r738kviola.fsf@fencepost.gnu.org>

> From: Glenn Morris <rgm@gnu.org>
> Cc: 16407@debbugs.gnu.org
> Date: Fri, 10 Jan 2014 15:11:45 -0500
> 
> 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.

As I said, this is generally impossible.

> (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.)

But what happens in reality is either the stomping or the manual is
renamed into emacs-xx, to allow several versions of manuals coexist.

> Sorry, I think it's overly complicated for this day-and-age, and could
> stand to be simplified.

I suggest to look at a typical Debian system with several Emacs
versions installed, and see what kind of arrangement they use.  At the
time, this was one of the reasons for the complexity.  Maybe it no
longer exists, I don't know.

In any case, the problem with being able to control where Emacs looks
for the misc manuals still exists, for those Emacs packages that are
developed and distributed separately.





  reply	other threads:[~2014-01-10 20:36 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
2014-01-10 20:36         ` Eli Zaretskii [this message]
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=838uunbmm2.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).