unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: Mathieu Lirzin <mthl@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: How to use Guix.el from Git?
Date: Sun, 22 Nov 2015 20:09:10 +0300	[thread overview]
Message-ID: <87d1v2otah.fsf@gmail.com> (raw)
In-Reply-To: <87mvu62pue.fsf@gnu.org> (Mathieu Lirzin's message of "Sun, 22 Nov 2015 13:14:33 +0100")

Mathieu Lirzin (2015-11-22 15:14 +0300) wrote:

> Hi,
>
> I would like to use the Guix.el from the Git repository of Guix, but I
> fail at configuring it.  I use Guix 0.9.0 built from source ontop of
> Debian and installed with standard the “/usr/local” prefix.
>
> It works perfectly with Guix.el from “/usr/local/share/emacs/site-lisp”
> with the configuration describe in the manual:
>
>   (add-to-list 'load-path "/usr/local/share/emacs/site-lisp")
>   (require 'guix-init)
>
> But when I try to replace this with the “Hacking” configuration from the
> manual:
>
>   (let ((dir "~/src/gnu/guix/emacs"))
>     (add-to-list 'load-path dir)
>     (setq guix-load-path dir))
>   (require 'guix-init nil t)

Hm, all I can say: this configuration works for me.

> I get this error when launching ‘M-x guix’:
>
>
> Backtrace:
> In ice-9/boot-9.scm:
>  157: 9 [catch #t #<catch-closure b12d60> ...]
> In unknown file:
>    ?: 8 [apply-smob/1 #<catch-closure b12d60>]
> In ice-9/boot-9.scm:
>   63: 7 [call-with-prompt prompt0 ...]
> In ice-9/eval.scm:
>  432: 6 [eval # #]
> In ice-9/boot-9.scm:
> 2401: 5 [save-module-excursion #<procedure e2a740 at ice-9/boot-9.scm:4045:3 ()>]
> 4050: 4 [#<procedure e2a740 at ice-9/boot-9.scm:4045:3 ()>]
> In unknown file:
>    ?: 3 [load-compiled/vm "/home/mthl/.cache/guile/ccache/2.0-LE-8-2.0/home/mthl/src/gnu/guix/emacs/guix-helper.scm.go"]
> In ice-9/boot-9.scm:
> 1724: 2 [%start-stack load-stack #<procedure d96580 at ice-9/boot-9.scm:1745:2 ()>]
> 1729: 1 [#<procedure d937b0 ()>]
> In unknown file:
>    ?: 0 [primitive-load-path "guix-main"]
>
> ERROR: In procedure primitive-load-path:
> ERROR: In procedure primitive-load-path: Unable to find file "guix-main" in load path

So Guix REPL is dead after this, right?  It looks like your
"~/src/gnu/guix/emacs" is not appended to guile %load-path (it is done
in `guix-start-repl' by cons-ing `guix-load-path' to
`geiser-guile-load-path').

Could you check "C-h v guix-load-path" to be sure that its value is
really "~/src/gnu/guix/emacs".  Also just in case, show the value of
`guix-helper-file' variable.

-- 
Alex

  reply	other threads:[~2015-11-22 17:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-22 12:14 How to use Guix.el from Git? Mathieu Lirzin
2015-11-22 17:09 ` Alex Kost [this message]
2015-11-22 18:20   ` Mathieu Lirzin
2015-11-22 21:05     ` Alex Kost
2015-11-22 21:15       ` Mathieu Lirzin
2015-11-23  8:35         ` Alex Kost

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=87d1v2otah.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mthl@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.
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).