Re: [PATCH] doc: Improve guile load path recommendation.

[myglc2 <myglc2@gmail.com>]

On 04/16/2017 at 11:06 Alex Kost writes:

> 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 ;-)

Thanks for the comments. I now see that I was confusing the effects of
installing guile 2.2, which causes recompilation of everything, with the
effects of this change, which I made at about the same time.

So please forget about the patch. SORRY for the run around!