From: Ricardo Wurmus <rekado@elephly.net>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: gwl-devel@gnu.org
Subject: Re: Guile code snippet
Date: Thu, 21 Apr 2022 22:46:20 +0200 [thread overview]
Message-ID: <87wnfiqhmd.fsf@elephly.net> (raw)
In-Reply-To: <87pmlaurla.fsf@laura>
Olivier Dion <olivier.dion@polymtl.ca> writes:
> On Thu, 21 Apr 2022, Ricardo Wurmus <rekado@elephly.net> wrote:
>>>> This is now fixed with commit
>>>> dceec9ecb9e24252ab9130f7a3626c00b2ff1a68.
>
> I tried this:
>
> process foo
> packages "guile" "guile-fibers"
> # /bin/guile {
> (use-modules (fibers))
> }
You’re missing “-c”. If you just use /bin/guile it expects a file name,
just like it does on the command line. This works fine:
process run
packages "guile" "guile-fibers"
# /bin/guile -c {
(use-modules (fibers))
}
> Also tried this:
>
> process foo
> packages "guile" "guile-fibers"
> procedure
> . `(begin
> (use-modules (fibers)))
I haven’t addressed this yet.
What happens here is that we are in fact setting GUILE_LOAD_PATH and
GUILE_LOAD_COMPILED_PATH (as we do for any search path specification
associated with the list of packages), but that has no impact on the
load path of the Guile process used to evaluate the expression.
I’ll investigate this.
--
Ricardo
next prev parent reply other threads:[~2022-04-21 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 3:37 Guile code snippet Olivier Dion via
2022-04-20 9:47 ` Ricardo Wurmus
2022-04-20 16:13 ` Olivier Dion via
2022-04-20 16:26 ` Ricardo Wurmus
2022-04-20 16:35 ` Olivier Dion via
2022-04-20 21:21 ` Ricardo Wurmus
2022-04-21 16:30 ` Olivier Dion via
2022-04-21 18:14 ` Ricardo Wurmus
2022-04-21 20:08 ` Olivier Dion via
2022-04-21 20:46 ` Ricardo Wurmus [this message]
2022-04-21 22:02 ` Olivier Dion via
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://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnfiqhmd.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=gwl-devel@gnu.org \
--cc=olivier.dion@polymtl.ca \
/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).