unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Amirouche Boubekki <amirouche@hypermove.net>
Cc: 23000-done@debbugs.gnu.org
Subject: bug#23000: update from wingo
Date: Mon, 20 Jun 2016 18:18:05 +0200	[thread overview]
Message-ID: <874m8ng7gi.fsf@pobox.com> (raw)
In-Reply-To: <26d9fb7cad72c6a91ad20a57e1651313@hypermove.net> (Amirouche Boubekki's message of "Tue, 03 May 2016 11:07:58 +0200")

tags 2300 +notabug
close
thanks

On Tue 03 May 2016 11:07, Amirouche Boubekki <amirouche@hypermove.net> writes:

> wingo said:
>
>> wingo | i don't think that's a guile bug -- i think in that case you
>> need to handle SIGPIPE
>> wingo | b/c posix is weird
>> wingo | (sigaction SIGPIPE SIG_IGN)
>> wingo | the web server does it.

Yep!





      reply	other threads:[~2016-06-20 16:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-12 18:57 bug#23000: send doesn't check for closed socket Amirouche Boubekki
2016-05-03  9:07 ` bug#23000: update from wingo Amirouche Boubekki
2016-06-20 16:18   ` Andy Wingo [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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874m8ng7gi.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=23000-done@debbugs.gnu.org \
    --cc=amirouche@hypermove.net \
    /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.
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).