From: Andreas Enge <andreas@enge.fr>
To: Alex Vong <alexvong1995@gmail.com>
Cc: 29826@debbugs.gnu.org
Subject: bug#29826: nondeterministic Broken pipe
Date: Sat, 23 Dec 2017 21:48:28 +0100 [thread overview]
Message-ID: <20171223204828.GA3290@jurong> (raw)
In-Reply-To: <874lohdwhb.fsf@gmail.com>
On Sun, Dec 24, 2017 at 04:23:44AM +0800, Alex Vong wrote:
> ERROR: In procedure display:
> ERROR: In procedure scm_flush: Broken pipe
Interesting! I get a different error message:
ERROR: In procedure display:
In procedure fport_write: Broken pipe
Andreas
next prev parent reply other threads:[~2017-12-23 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 20:23 bug#29826: nondeterministic Broken pipe Alex Vong
2017-12-23 20:48 ` Andreas Enge [this message]
2017-12-24 8:37 ` Alex Vong
2017-12-24 22:11 ` Mark H Weaver
2017-12-25 14:02 ` Alex Vong
2017-12-31 10:11 ` Ludovic Courtès
2018-01-02 12:07 ` Alex Vong
2018-01-02 19:04 ` Mark H Weaver
2018-01-02 22:17 ` Ludovic Courtès
2018-02-14 12:21 ` Oleg Pykhalov
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=20171223204828.GA3290@jurong \
--to=andreas@enge.fr \
--cc=29826@debbugs.gnu.org \
--cc=alexvong1995@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).