From: Andy Wingo <wingo@pobox.com>
To: Daniel Hartwig <mandyke@gmail.com>
Cc: guile-user@gnu.org, Thien-Thi Nguyen <ttn@gnuvola.org>
Subject: Re: Filter IO through an external command
Date: Fri, 24 Feb 2012 11:25:28 +0100 [thread overview]
Message-ID: <8762ewmstj.fsf@pobox.com> (raw)
In-Reply-To: <CAN3veRdEwX6QRfwi77KcWP7Vi6NTGjNiHQyOayTcSjLSxVeUrA@mail.gmail.com> (Daniel Hartwig's message of "Fri, 24 Feb 2012 11:31:40 +0800")
On Fri 24 Feb 2012 04:31, Daniel Hartwig <mandyke@gmail.com> writes:
> I ended up using run-with-pipe from guile-lib's (os process) module
> which returns separate port objects--similar to the OP's proc..
Should we incorporate something like this into Guile?
Want to make a patch? It could make open-process return the read and
write ports separately.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-02-24 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 14:26 Filter IO through an external command Tristan Colgate
2012-02-23 17:16 ` Thien-Thi Nguyen
2012-02-23 17:16 ` Thien-Thi Nguyen
2012-02-24 3:31 ` Daniel Hartwig
2012-02-24 10:25 ` Andy Wingo [this message]
2012-02-27 6:33 ` Daniel Hartwig
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=8762ewmstj.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=mandyke@gmail.com \
--cc=ttn@gnuvola.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).