Alex Kost (2015-09-10 00:24 +0300) wrote:
> Ludovic Courtès (2015-09-09 23:11 +0300) wrote:
>
>> Alex Kost skribis:
>>
>>> As a workaround for this issue it was proposed¹ to transform
>>> ‘current-build-output-port’ into a procedure (I have checked that it
>>> solves the problem). What do you th
Ludovic Courtès (2015-09-09 23:11 +0300) wrote:
> Alex Kost skribis:
>
>> As a workaround for this issue it was proposed¹ to transform
>> ‘current-build-output-port’ into a procedure (I have checked that it
>> solves the problem). What do you think about it? Perhaps to make sure
>> that the por
Alex Kost skribis:
> As a workaround for this issue it was proposed¹ to transform
> ‘current-build-output-port’ into a procedure (I have checked that it
> solves the problem). What do you think about it? Perhaps to make sure
> that the port will be always the same define it like this:
>
> (defi
Ludovic Courtès (2015-09-07 00:28 +0300) wrote:
> Alex Kost skribis:
>
>> Now the bug itself:
>>
>> 1. Start Geiser (M-x run-guile)
>>
>> 2. Make a scheme buffer and evaluate (use-modules (guix scripts build))
>>there using "C-x C-e" or "C-M-x" (or any other "geiser-eval-…"
>>command). T
Ludovic Courtès (2015-09-07 00:28 +0300) wrote:
> Alex Kost skribis:
>
>> Now the bug itself:
>>
>> 1. Start Geiser (M-x run-guile)
>>
>> 2. Make a scheme buffer and evaluate (use-modules (guix scripts build))
>>there using "C-x C-e" or "C-M-x" (or any other "geiser-eval-…"
>>command). T
Alex Kost skribis:
> Now the bug itself:
>
> 1. Start Geiser (M-x run-guile)
>
> 2. Make a scheme buffer and evaluate (use-modules (guix scripts build))
>there using "C-x C-e" or "C-M-x" (or any other "geiser-eval-…"
>command). This is important: do not ,use module in the REPL;
>eval
Hello.
There is a strange problem with evaluating a code using Geiser, which
leads to some missing output in a REPL. I have an example demonstrating
the problem using some Guix code, but I would like to have a pure guile
recipe, so that it can be reported.
So how to reproduce the bug. At first,
