From: ludo@gnu.org (Ludovic Courtès)
To: Luther Thompson <lutheroto@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Command-line info sees more stuff than Emacs info
Date: Mon, 27 Nov 2017 16:00:17 +0100 [thread overview]
Message-ID: <87indvlqbi.fsf@gnu.org> (raw)
In-Reply-To: <1511737214.2196.14.camel@pentos> (Luther Thompson's message of "Sun, 26 Nov 2017 18:00:14 -0500")
Hi,
Luther Thompson <lutheroto@gmail.com> skribis:
> The Emacs info-mode can't see all of the info files on my system. Most
> notably, it doesn't see coreutils. The command-line info seems to see
> everything just fine.
>
> I'm running Trisquel+Guix. I use the info and coreutils that came with
> Trisquel, while Emacs is installed with Guix.
[...]
> export INFOPATH="${GUIX_PROFILE:-/gnu/store/38lybr3lz7d2i1pqx9p025jiinxcpa8m-profile}/share/info${INFOPATH:+:}$INFOPATH"
Most likely the problem is that ‘info’ from Trisquel looks for manuals
in /usr/share/info by default, where Emacs from Guix does not.
The fix is to add /usr/share/info to INFOPATH (and/or
‘Info-directory-list’ in Emacs.)
Could you check whether that solves the problem?
Ludo’.
next prev parent reply other threads:[~2017-11-27 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 23:00 Command-line info sees more stuff than Emacs info Luther Thompson
2017-11-27 15:00 ` Ludovic Courtès [this message]
2017-11-28 8:49 ` Luther Thompson
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=87indvlqbi.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=lutheroto@gmail.com \
/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.
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).