From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: bug-guile@gnu.org
Subject: Re: open-output-pipe problem
Date: Thu, 01 Aug 2002 13:13:18 -0700 [thread overview]
Message-ID: <E17aMJy-00066S-00@giblet> (raw)
In-Reply-To: message from Satoru Takabayashi on Sat, 13 Jul 2002 22:56:57 +0900
From: Satoru Takabayashi <satoru@namazu.org>
Date: Sat, 13 Jul 2002 22:56:57 +0900
I tried guile 1.4.1 and found a problem on open-output-pipe.
hi, thanks for the bug report. i have reproduced the problem and
noticed that it is gone in guile-HEAD, but have not yet figured out
which of the (many) changes is responsible for the fixed behavior.
i plan to devote some hours looking into this because it is an area of
libguile i'd like to learn more about. will let you know what i find.
thi
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next reply other threads:[~2002-08-01 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 20:13 Thien-Thi Nguyen [this message]
2002-08-08 3:20 ` open-output-pipe problem Thien-Thi Nguyen
2002-08-09 1:08 ` Thien-Thi Nguyen
-- strict thread matches above, loose matches on Subject: below --
2002-07-13 13:56 Satoru Takabayashi
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=E17aMJy-00066S-00@giblet \
--to=ttn@giblet.glug.org \
--cc=bug-guile@gnu.org \
--cc=ttn@glug.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.
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).