From: Andy Wingo <wingo@pobox.com>
To: Mike Gran <spk121@yahoo.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: setvbuf can't make it unbuffered
Date: Thu, 14 Mar 2013 09:58:29 +0100 [thread overview]
Message-ID: <87ip4ucq8a.fsf@pobox.com> (raw)
In-Reply-To: <1363232296.83746.YahooMailNeo@web120403.mail.ne1.yahoo.com> (Mike Gran's message of "Wed, 13 Mar 2013 20:38:16 -0700 (PDT)")
Hi :)
On Thu 14 Mar 2013 04:38, Mike Gran <spk121@yahoo.com> writes:
>> From: Andy Wingo <wingo@pobox.com>
>
>>I made some notes there.
>>
>
> I noticed in your comments to Nala G that you recommend using
> `print-exception'. Is that intended to be public API? It doesn't
> appear in the manual.
It is intended to be public, yes. So many bugs!
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2013-03-14 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 11:05 setvbuf can't make it unbuffered Nala Ginrut
2013-03-13 13:08 ` Andy Wingo
2013-03-13 14:39 ` Nala Ginrut
2013-03-14 3:38 ` Mike Gran
2013-03-14 8:58 ` Andy Wingo [this message]
2013-03-14 9:38 ` Nala Ginrut
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=87ip4ucq8a.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=spk121@yahoo.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.
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).