From: Yoshinori Arai <kumagusu08@gmail.com>
To: Alex Kost <alezost@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: emacs-guix error
Date: Wed, 30 Jan 2019 16:29:31 +0900 [thread overview]
Message-ID: <20190130072931.d3rtzbtgekjibhbe@WaraToNora> (raw)
In-Reply-To: <87a7jlov1h.fsf@gmail.com>
On Mon, Jan 28, 2019 at 02:56:10PM +0300, Alex Kost wrote:
> Maxim Cournoyer (2019-01-27 20:49 -0500) wrote:
>
> > Hello!
> >
> > [...]
> >
> >> Are you using Guix from a git checkout? In that case you’ll need to
> >> recompile as there has been an ABI change.
> >
> > My normal Guix run from guix pull, but I do have a Guix checkout that I
> > use with the pre-inst-env wrapper.
> >
> > I have this set in my ~/.emacs.
> >
> > (setq guix-directory "~/src/guix")
> >
> > IIUC, that doesn't cause Emacs-Guix to use that Guix, only locate
> > package definition.
>
> This is correct. If someone wants to augment the default load path used
> by Emacs-Guix, they can set 'guix-load-path' variable.
>
> --
> Alex
>
I can recovered.
I set (setq guix-guile-program "guile") in my user-config of dot.spacemacs and restart emacs.
It's same as to set environment variable, GUILE_AUTO_COMPILE="fresh".
next prev parent reply other threads:[~2019-01-30 7:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 1:30 emacs-guix error brettg
2019-01-28 1:39 ` brettg
2019-01-28 7:50 ` Ricardo Wurmus
2019-01-28 1:49 ` Maxim Cournoyer
2019-01-28 11:56 ` Alex Kost
2019-01-30 7:29 ` Yoshinori Arai [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-24 2:34 brettg
2019-01-25 17:48 ` Alex Kost
2019-01-24 0:20 Yoshinori Arai
2019-01-25 17:48 ` Alex Kost
2019-01-26 3:31 ` Yoshinori Arai
2019-01-26 17:29 ` Alex Kost
2019-01-26 20:50 ` Maxim Cournoyer
2019-01-26 21:25 ` Ricardo Wurmus
2019-01-28 11:22 ` Yoshinori Arai
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=20190130072931.d3rtzbtgekjibhbe@WaraToNora \
--to=kumagusu08@gmail.com \
--cc=alezost@gmail.com \
--cc=help-guix@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).