Alex Kost <alez...@gmail.com> skribis:
> Ludovic Courtès (2015-08-18 17:05 +0300) wrote:
[...]
>>> +want to use a module it defines, so you switch to the Geiser REPL and
>>> +write @code{,use (some module)} there. You may just use this command
>>> +instead.
>>
>> Could you mention a use case here? Like:
>>
>> For instance, you may call this command while visiting a file that
>> defines packages; you can then switch to the associated REPL with
>> @kbd{C-c C-z}, which will be in the current module, which is handy.
>
> The REPL will not be in the current module. "M-x
> guix-devel-use-current-module" is the equivalent of ",use", not
> ",module". I thought the documentation was clear about that, no?
Now that I reread it, it seems clear, indeed. Forget my previous
comment.
>> The “-devel” part might make it sound like it has an effect similar to
>> ‘pre-inst-env’ though. Perhaps we should explicitly remind developers
>> that they must set ‘guix-load-path’ appropriately?
>
> Setting ‘guix-load-path’ will not take any effect here. The whole point
> of this guix-devel stuff is to provide additional commands for
> scheme-mode, like Geiser does. And these additional commands are
> independent from Guix REPL; they are called in the current Geiser REPL
> the same way you would use other Geiser commands.
Right, sorry for messing things up!
Thanks,
Ludo’.
