unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Adam Porter <adam@alphapapa.net>
To: 39984@debbugs.gnu.org
Subject: bug#39984: INFOPATH set in /etc/profile.d/guix.sh should end in ":" for Emacs's sake
Date: Sun, 8 Mar 2020 08:31:24 -0500	[thread overview]
Message-ID: <CAO_b3FWuKszWm-P25nXzoNoLAuhGdVJ3VsuaXiUrpfDRWfnnOw@mail.gmail.com> (raw)

I installed Guix into my system, and I've been enjoying using it.
However, I found that, after installing it, when I logged out and back
in, and then started Emacs, Emacs could no longer see my system's info
pages (including Emacs's own info pages).  I found that the Emacs
variable Info-directory-list only contained
"/home/me/.config/guix/current/share/info", so it couldn't see the
info pages in "/usr/local/share/info/" and "/usr/share/info/".
According to the Info-directory-list docstring:

If nil, meaning not yet initialized, Info uses the environment
variable INFOPATH to initialize it, or ‘Info-default-directory-list’
if there is no INFOPATH variable in the environment, or the
concatenation of the two if INFOPATH ends with a ‘path-separator’.

I found that INFOPATH is being set in /etc/profile.d/guix.sh, which does this:

  # Export INFOPATH so that the updated info pages can be found
  # and read by both /usr/bin/info and/or $GUIX_PROFILE/bin/info
  export INFOPATH="$_GUIX_PROFILE/share/info${INFOPATH:+:}$INFOPATH"

Since it does not append a colon at the end, Emacs doesn't add the
directories from Info-default-directory-list.  I added a colon to the
end and restarted Emacs, and it fixed the problem.

So I'd suggest adding ":" to the end of INFOPATH in /etc/profile.d/guix.sh.

Thanks.

             reply	other threads:[~2020-03-08 13:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-08 13:31 Adam Porter [this message]
2020-03-21 23:04 ` bug#39984: INFOPATH set in /etc/profile.d/guix.sh should end in ":" for Emacs's sake Ludovic Courtès

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=CAO_b3FWuKszWm-P25nXzoNoLAuhGdVJ3VsuaXiUrpfDRWfnnOw@mail.gmail.com \
    --to=adam@alphapapa.net \
    --cc=39984@debbugs.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/guix.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).