From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-user@gnu.org
Subject: Re: open-input-pipe messes with output buffers
Date: Thu, 29 Aug 2002 13:11:57 -0700 [thread overview]
Message-ID: <E17kVe1-0007Tj-00@giblet> (raw)
In-Reply-To: <w53bs7lldt4.fsf@woozle.org> (message from Neale Pickett on 29 Aug 2002 11:28:39 -0700)
From: Neale Pickett <neale@woozle.org>
Date: 29 Aug 2002 11:28:39 -0700
[rebuffering weirdness w/ popen + test case]
Is this the desired behavior?
older versions of guile did not separate fdes and port handling properly
when doing pipe operations. guile-1.4.1.8 DTRT, for example. to try:
wget http://www.glug.org/tmp/2002-08/guile-1.4.1.8.tar.gz
tar xzf guile-1.4.1.8.tar.gz
cd guile-1.4.1.8 && ./configure --prefix /tmp/a/b/c && make install
alias guile=/tmp/a/b/c/bin/guile
i believe 1.5.x works too, but i don't recommend that for other reasons.
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2002-08-29 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 18:28 open-input-pipe messes with output buffers Neale Pickett
2002-08-29 20:11 ` Thien-Thi Nguyen [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=E17kVe1-0007Tj-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-user@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).