From: Maxime Devos <maximedevos@telenet.be>
To: Attila Lendvai <attila@lendvai.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: using an SRFI that is not available in Guile
Date: Fri, 14 Jan 2022 13:02:58 +0100 [thread overview]
Message-ID: <2419d6d5f2bdbbb51ea514077a545919dc816dff.camel@telenet.be> (raw)
In-Reply-To: <Vt7J6sH5XQ5vPBI9nWWId72aGogII9iKT1crBI1jV9U03uBcTFy2YxOubDK67SSnKgYmmNeFCvIXDFwZSBVa_eo1MQbU62RQLij4tHQKYV4=@lendvai.name>
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
Attila Lendvai schreef op do 13-01-2022 om 18:20 [+0000]:
> > Using the guile REPL is a little less complicated than the guix
> > repl,
> > I would recommend trying
> >
> > "./pre-inst-env guix shell guile-srfi-189 -- guile" first.
>
> no luck with this either:
>
> $ ./pre-inst-env guix build guile-srfi-189
I forgot to include "guile" ("guix shell" needs that to know
"GUILE_LOAD{,_COMPILED}_PATH"), try
./pre-inst-env guix shell guile guile-srfi-189 -- guile
instead.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-01-14 12:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 16:46 using an SRFI that is not available in Guile Attila Lendvai
2022-01-12 17:01 ` Attila Lendvai
2022-01-12 17:09 ` Maxime Devos
2022-01-13 9:55 ` Attila Lendvai
2022-01-13 10:49 ` Maxime Devos
2022-01-13 18:20 ` Attila Lendvai
2022-01-13 20:48 ` Attila Lendvai
2022-01-14 12:02 ` Maxime Devos [this message]
2022-01-17 13:45 ` Attila Lendvai
2022-01-13 10:53 ` Maxime Devos
2022-01-13 10:56 ` Maxime Devos
2022-01-18 15:09 ` Ludovic Courtès
2022-01-18 17:06 ` Attila Lendvai
2022-01-19 10:34 ` Ludovic Courtès
2022-01-21 13:59 ` Attila Lendvai
2022-01-24 15:41 ` Ludovic Courtès
2022-01-24 23:02 ` Attila Lendvai
2022-02-05 11:13 ` Ludovic Courtès
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=2419d6d5f2bdbbb51ea514077a545919dc816dff.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=attila@lendvai.name \
--cc=guix-devel@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).