From: Einar Largenius <jaadu@lysator.liu.se>
To: Fredrik Salomonsson <plattfot@posteo.net>
Cc: Guix mailing list <help-guix@gnu.org>
Subject: Re: Setting up a geiser development environment
Date: Tue, 31 May 2022 20:26:54 +0200 [thread overview]
Message-ID: <87r149ms0x.fsf@lysator.liu.se> (raw)
In-Reply-To: <87tu9apcrc.fsf@posteo.net>
Hi, thanks for the reply.
I want to have geiser accessible. It would make trailing and error and
finding symbols much easier.
> (use-modules (gnu packages))
I forgot to include this in my example. The Geiser repl tells me there are
no code for the module. It works fine when using guix repl though.
I checked the value of %load-path when I start geiser and compare it
with the value I get with guix repl. They look very similar except the
load path provided with guix repl is provides an additional path:
"/gnu/store/6qfk8gs9qyk5vx79bb62gf4gz9n7wp95-guix-module-union/share/guile/site/3.0"
I don't find anything similar in my .guix-profile.
I see a few alternatives.
1. Identify which package includes this "guix-module-union" and add it
to my profile.
2. Dynamically add the path using wildcards to my .guile startup file.
Adding a hardcoded path will break this during every update.
3. Change so that geiser uses "guix repl" instead of "guile" when
starting a repl.
I lack the experience with both guix and scheme so none of the above
would be easy to do for me. The last alternative would probably be the
easiest for me.
--
Med vänliga hälsningar Einar
next prev parent reply other threads:[~2022-05-31 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 18:22 Setting up a geiser development environment Einar Largenius
2022-05-28 3:16 ` Fredrik Salomonsson
2022-05-31 18:26 ` Einar Largenius [this message]
2022-06-01 19:02 ` Fredrik Salomonsson
2022-05-28 17:31 ` Tobias Geerinckx-Rice
2022-05-28 18:02 ` Tobias Geerinckx-Rice
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=87r149ms0x.fsf@lysator.liu.se \
--to=jaadu@lysator.liu.se \
--cc=help-guix@gnu.org \
--cc=plattfot@posteo.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.
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).