unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: (Geiser or guile bug) Guix-daemon output is missing
Date: Thu, 10 Sep 2015 19:44:28 +0300	[thread overview]
Message-ID: <87egi6usur.fsf@gmail.com> (raw)
In-Reply-To: <871te7s2vh.fsf@gmail.com> (Alex Kost's message of "Thu, 10 Sep 2015 00:24:02 +0300")

Alex Kost (2015-09-10 00:24 +0300) wrote:

> Ludovic Courtès (2015-09-09 23:11 +0300) wrote:
>
>> Alex Kost <alezost@gmail.com> 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:
>>>
>>> (define current-build-output-port (memoize current-error-port))
>>>
>>> Is it acceptable?
>>
>> No, ‘current-build-output-port’ should remain a SRFI-39 parameter so
>> that callers can easily rebind it.
>>
>> However, perhaps the guix.el code could do:
>>
>>   (current-build-output-port (current-error-port))
>>
>> at startup; would that be doable?
>
> (IMO it would be so ugly, that I should say: "no")

After thinking more, I had an idea how to make a not-so-ugly workaround,
so "yes", I think I'll do a workaround on elisp side.

-- 
Alex

      reply	other threads:[~2015-09-10 16:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-06  9:03 (Geiser or guile bug) Guix-daemon output is missing Alex Kost
2015-09-06 21:28 ` Ludovic Courtès
2015-09-07 19:58   ` Alex Kost
2015-09-09 16:47   ` Alex Kost
2015-09-09 20:11     ` Ludovic Courtès
2015-09-09 21:24       ` Alex Kost
2015-09-10 16:44         ` Alex Kost [this message]

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=87egi6usur.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /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).