From: Alex Kost <alezost@gmail.com>
To: myglc2 <myglc2@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] doc: Improve guile load path recommendation.
Date: Sun, 16 Apr 2017 11:06:44 +0300 [thread overview]
Message-ID: <87tw5ord2j.fsf@gmail.com> (raw)
In-Reply-To: <86pogdugqz.fsf@gmail.com> (myglc2@gmail.com's message of "Sun, 16 Apr 2017 00:19:00 -0400")
myglc2 (2017-04-16 00:19 -0400) wrote:
> On 04/15/2017 at 16:20 Chris Marusich writes:
[...]
> The geiser doc says ...
>
> You can also specify a couple more initialisation parameters. For
> Guile, 'geiser-guile-load-path' is a list of paths to add to its load
> path (and its compiled load path) when it's started, ...
>
> ... which implies that geiser sets the compiled load path to the
> geiser-guile-load-path. But it does not seem to be doing that. I guess
> that could be a bug.
Previously I also thought that setting ‘geiser-guile-load-path’ is not
enough as it would only set the %load-path, because Geiser starts Guile
like this (<some-dir> comes from ‘geiser-guile-load-path’):
guile ... -L <some-dir>
while it should be:
guile ... -L <some-dir> -C <some-dir>
to set the %load-compiled-path as well. However, I've just found that
geiser sets %load-compiled-path internally in its Scheme code, so the
current recommendation in the manual should probably work (I didn't
check it, as I prefer to set environment variables).
BTW, according to the commit message at
<https://github.com/jaor/geiser/commit/393305d2fcf612f4e5f99383f680f819b458c326>,
it looks like Ludovic was the person who proposed this change ;-)
--
Alex
next prev parent reply other threads:[~2017-04-16 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 19:17 [PATCH] doc: Improve guile load path recommendation myglc2
2017-04-15 23:20 ` Chris Marusich
2017-04-16 4:19 ` myglc2
2017-04-16 8:06 ` Alex Kost [this message]
2017-04-16 13:24 ` myglc2
2017-04-17 1:57 ` Chris Marusich
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=87tw5ord2j.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=myglc2@gmail.com \
/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).