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: Tue, 29 Sep 2015 09:40:56 +0200 [thread overview]
Message-ID: <87io6t3c6v.fsf@gnu.org> (raw)
In-Reply-To: <56096A16.4020703@fastmail.net> (Konrad Hinsen's message of "Mon, 28 Sep 2015 18:25:58 +0200")
Hello,
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
> I have just set up a virtual machine for test-driving Guix as a
> software development and deployment tool in scientific computing. I
> found the Guix SD to be a bit too minimal for my needs, so I started
> from a minimal Debian 8 system and added the Guix package manager. I
> haven't done anything else but installing software until now, but so
> far it looks very good!
Thanks for your kind words, and welcome!
> So is there a Guix-y way to add info files from packages to Emacs'
> info directory?
When software is installed in a profile, Guix automatically updates the
‘dir’ file in that profile.
Then you really have to set INFOPATH accordingly, because otherwise
there’s no way Emacs (or even the standalone reader, I would expect)
could find them. On GuixSD, INFOPATH is set to
$HOME/.guix-profile/share/info:/run/current-system/profile/share/info.
If you do so, C-h i will open ~/.guix-profile/share/info/dir and you’ll
be happy. ;-)
Note that depending on how you installed Guix itself, its manual is
elsewhere. That location must also be added to INFOPATH.
HTH!
Ludo’.
next prev parent reply other threads:[~2015-09-29 7:41 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 [this message]
2015-09-30 6:26 ` Konrad Hinsen
2015-10-01 12:13 ` Ludovic Courtès
-- 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
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=87io6t3c6v.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 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).