unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Luther Thompson <lutheroto@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: Command-line info sees more stuff than Emacs info
Date: Tue, 28 Nov 2017 03:49:16 -0500	[thread overview]
Message-ID: <1511858956.5334.9.camel@pentos> (raw)
In-Reply-To: <87indvlqbi.fsf@gnu.org>


On Mon, 2017-11-27 at 16:00 +0100, Ludovic Courtès wrote:
> 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.)

Changing INFOPATH does seem to work. I guess Emacs ignores the 'PATH'
component of INFOPATH.

On re-reading about the --directory option [0], I found that to add the
built-in default info directories, I just had to put this line:

export INFOPATH="$INFOPATH:"

...after running the Guix profile. This works for both the stand-alone
info and Emacs info.

Thanks for the help!

Luther

[0]
https://www.gnu.org/software/texinfo/manual/info-stnd/html_node/Invoking-Info.html

      reply	other threads:[~2017-11-28 15:41 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
2017-11-28  8:49   ` Luther Thompson [this message]

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=1511858956.5334.9.camel@pentos \
    --to=lutheroto@gmail.com \
    --cc=ludo@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.
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).