unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.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: Sat, 23 Apr 2022 16:28:19 +0200	[thread overview]
Message-ID: <87tuajri0s.fsf@gnus.org> (raw)
In-Reply-To: <d038kwjsn4.fsf@fencepost.gnu.org> (Glenn Morris's message of "Fri, 10 Jan 2014 00:46:39 -0500")

Glenn Morris <rgm@gnu.org> writes:

> The initialization of Info-directory-list is rather complicated.
> Part of it uses this logic:
>
>    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

I agree completely.

The info setup is pretty convoluted, so I'm not quite sure what the
current state is.  This is the default value in "emacs -Q" in Emacs 29:

Info-directory-list
("/home/larsi/src/emacs/trunk/info/" "/usr/share/info/")

But it's with an uninstalled Emacs.  Reading Info-default-dirs, it looks
like it's trying to do the right thing?  So has this been solved already
at some point?

> (even before INFOPATH entries).

But I'm not sure about that.  I don't think distributions set that by
default, but users do to alter stuff, so we should respect it.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2022-04-23 14:28 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
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 [this message]
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=87tuajri0s.fsf@gnus.org \
    --to=larsi@gnus.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).