From: ludo@gnu.org (Ludovic Courtès)
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: guix-devel@gnu.org
Subject: Re: Viewing the Guix manual in Emacs under Guix
Date: Thu, 01 Oct 2015 14:13:54 +0200 [thread overview]
Message-ID: <8737xupz0d.fsf@gnu.org> (raw)
In-Reply-To: <22027.32911.979428.195670@Ordinateur-de-Catherine--Konrad.local> (Konrad Hinsen's message of "Wed, 30 Sep 2015 08:26:23 +0200")
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
> I hadn't noticed the global 'dir' before. So, yes,
>
> INFOPATH=$GUIX_PROFILE/share/info
>
> is enough to make everything work. But is there a good reason not
> to include this setting in $GUIX_PROFILE/etc/profile ?
Actually I just found there’s no good reason!
$GUIE_PROFILE/etc/profile is generated based on the environment
variables claimed by the installed packages (for instance Python claims
‘PYTHONPATH’, and so on.) It turns out that neither Texinfo nor Emacs
claims ‘INFOPATH’.
I’ve fixed that for Emacs (commit 64c983) and will fix it in the next
core update cycle for Texinfo. So now, when Emacs is in the profile,
etc/profile contain the ‘INFOPATH’ setting.
> > there’s no way Emacs (or even the standalone reader, I would expect)
>
> The standalone reader does find everything. Even the one from my basic
> Debian install finds the Guix manual, although I can't say how.
Hmm, interesting.
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-10-01 12:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 16:25 Viewing the Guix manual in Emacs under Guix Konrad Hinsen
2015-09-29 7:40 ` Ludovic Courtès
2015-09-30 6:26 ` Konrad Hinsen
2015-10-01 12:13 ` Ludovic Courtès [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-30 1:02 Vicente Vera
2015-10-01 9:29 ` Ricardo Wurmus
2015-10-01 18:12 ` Vicente Vera
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=8737xupz0d.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=konrad.hinsen@fastmail.net \
/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/guix.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.