unofficial mirror of 
 help / color / mirror / Atom feed
From: Olivier Dion via <>
To: Csepp <>
Subject: Re: Configuring geiser for load paths of Guix environment
Date: Tue, 02 Aug 2022 12:46:52 -0400	[thread overview]
Message-ID: <87wnbqzj7n.fsf@laura> (raw)
In-Reply-To: <>

On Tue, 02 Aug 2022, Csepp <> wrote:
> Olivier Dion via <> writes:
>> Hi,
>> Say I have a .guix.scm in my project with something like
>> (specifications->manifest (list "guile" "guile-fibers" "guile-gcrypt"))
>> If I want to develop with Geiser, it needs to find these modules in its
>> load paths.  My solution to this problem is the following .geiser at the
>> project root:
>> ;; -*-Scheme-*-
>> (let* ((port ((@@ (ice-9 popen) open-input-pipe)
>>               "guix shell -m .guix.scm -- /bin/sh -c 'echo $GUIX_ENVIRONMENT'"))
>>        (profile ((@@ (ice-9 rdelim) read-line) port)))
>>   (add-to-load-path (string-append profile "/share/guile/site/3.0"))
>>   (set! %load-compiled-path
>>         (cons (string-append profile "/lib/guile/3.0/site-ccache")
>>               %load-compiled-path)))
>> I'm wondering if someone has a better solution to this?
> I'm not an Emacs guru, so this might suck, but what I did is simply set
> the related variable.  Forgot what it was, but its contents were "guile"
> and I changed it to '("guix" "repl") and it worked.  You could probably
> do something like '("guix" "shell" "-m" "guix.scm" "--" "guile") .

I finally end up doing something similar.

In .dir-locals.el:
`((nil . ((geiser-guile-binary . "./.geiser-guile"))))'

In .geiser-guile:
exec guix shell --pure -D -f .guix/packages.scm -- guile $@


Olivier Dion

      reply	other threads:[~2022-08-02 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 16:24 Olivier Dion via
2022-08-01 23:25 ` Csepp
2022-08-02 16:46   ` Olivier Dion via [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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wnbqzj7n.fsf@laura \ \ \ \

* 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).