all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Howard Melman <hmelman@gmail.com>,
	larsi@gnus.org, 54961@debbugs.gnu.org, juri@linkov.net
Subject: bug#54961: 28.1; info-display-manual completions issues
Date: Wed, 20 Apr 2022 18:01:16 +0100	[thread overview]
Message-ID: <YmA8XMuTj2U3Kf54@idiocy.org> (raw)
In-Reply-To: <835yn5ui65.fsf@gnu.org>

On Tue, Apr 19, 2022 at 07:55:30PM +0300, Eli Zaretskii wrote:
> > on emacs -Q (on mac)
> > 
> > Info-default-directory-list
> > ("/Applications/GnuEmacs.app/Contents/Resources/info/" "/usr/local/share/info/" "/usr/share/info/")
> > 
> > after running C-h i, Info-directory-list is the same
> > ("/Applications/GnuEmacs.app/Contents/Resources/info/" "/usr/local/share/info/" "/usr/share/info/")
<snip>
> But then info-initialize, which is supposed to implement the above,
> deviates from that behavior on macOS, with this commentary:
> 
>       ;; For a self-contained (ie relocatable) NS build, AFAICS we
>       ;; always want the included info directory to be at the head of
>       ;; the search path, unless it's already in INFOPATH somewhere.
>       ;; It's at the head of Info-default-directory-list,
>       ;; but there's no way to get it at the head of Info-directory-list
>       ;; except by doing it here.
> 
> I cannot say I understand this reasoning, and neither do I understand
> whether this explains what you see in your case (because I don't know
> what is meant by "self-contained i.e. relocatable NS build".

I'm not sure what the reasoning is either.

The self-contained build is where all Emacs's files are installed in a
special directory, in this case "/Applications/GnuEmacs.app" which can
be placed anywhere on the filesystem and run from the GUI.

My uneducated guess is that it's possible to have a "UNIX" style
install already on a machine, which might be in /usr and then want to
run the self-contained version and not pick up the files in /usr
before the self-contained version's files.

I've no idea if that's plausible.

It looks like Glen's included a couple of links about why this was
done in change eb7afdaddc286b57253cf0cd643b2ea594fb130c.
-- 
Alan Third





  parent reply	other threads:[~2022-04-20 17:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15 19:04 bug#54961: 28.1; info-display-manual completions issues Howard Melman
2022-04-16  9:39 ` Lars Ingebrigtsen
2022-04-16 11:27   ` Howard Melman
2022-04-16 14:00     ` Lars Ingebrigtsen
2022-04-16 14:38 ` Lars Ingebrigtsen
2022-04-16 15:21   ` Howard Melman
2022-04-16 15:23     ` Lars Ingebrigtsen
2022-04-18 19:02     ` Juri Linkov
2022-04-18 19:45       ` Howard Melman
2022-04-18 21:28       ` Howard Melman
2022-04-19  5:35         ` Eli Zaretskii
2022-04-19 13:27           ` Howard Melman
2022-04-19 16:55             ` Eli Zaretskii
2022-04-19 18:43               ` Howard Melman
2022-04-19 18:55                 ` Eli Zaretskii
2022-04-19 19:28                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-20  5:39                     ` Eli Zaretskii
2022-04-20 12:00                       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-20 12:38                         ` Eli Zaretskii
2022-04-19 19:07                 ` Howard Melman
2022-04-19 19:24                   ` Eli Zaretskii
2022-04-19 19:24                   ` Juri Linkov
2022-04-20 17:01               ` Alan Third [this message]
2022-04-20 19:10                 ` Howard Melman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YmA8XMuTj2U3Kf54@idiocy.org \
    --to=alan@idiocy.org \
    --cc=54961@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=hmelman@gmail.com \
    --cc=juri@linkov.net \
    --cc=larsi@gnus.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.