unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 16:03:22 -0500	[thread overview]
Message-ID: <fo8uunmtwl.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <838uunbmm2.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Jan 2014 22:36:21 +0200")

Eli Zaretskii wrote:

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

They install the info pages into /usr/share/info/emacs-N (sensible).
And then they patch info.el so that it finds those first:

http://patch-tracker.debian.org/patch/series/view/emacs24/24.3+1-2/0001-Prefer-usr-share-info-emacs-24-over-usr-share-info.patch

So whatever info.el thought it was doing to suit Debian, it wasn't
enough anyway.

They should not have to have such a patch, it should work out of the box.

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

I disagree that this is an issue.

1) No problem at all with package.el, before or after any change to info.el.

2) I have no data, but doubt this was a problem people were solving via
INFOPATH anyway.

3) To use a newer version of a built-in package, you have to customize
load-path. I maintain that it's fine to expect people to have to
customize Info-directory-list similarly. (Perhaps this part of info.el
should be preloaded to make this easier.)





  reply	other threads:[~2014-01-10 21:03 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
2014-01-10 21:03           ` Glenn Morris [this message]
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=fo8uunmtwl.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).