unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: guile-user <guile-user@gnu.org>
Subject: Re: Pipes and processes, stdin, stdout and stderr
Date: Wed, 15 Apr 2015 23:38:06 +0200	[thread overview]
Message-ID: <87r3rlul4p.fsf@zigzag.favinet> (raw)
In-Reply-To: <873842yahs.fsf@earlgrey.lan> (Christopher Allan Webber's message of "Mon, 13 Apr 2015 19:17:41 -0500")

[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]

() Christopher Allan Webber <cwebber@dustycloud.org>
() Mon, 13 Apr 2015 19:17:41 -0500

   It might be really nice if there was a way to access stdin,
   stdout, and stderr as separate ports.  I might be willing to
   write some code for it, if someone could point me in the
   right direction.  But I really don't know where to look.

IIRC, ttn-do (http://www.gnuvola.org/software/ttn-do/) has a
child process module ‘(ttn-do zzz subprocess)’ that supports
such access.  It is not as automagic as ‘(ice-9 popen)’, but
maybe that's the right level for you.  If you look at the code
of both modules (highly encouraged :-D), you will see a fairly
similar pattern.  I think the best way forward is if Someone
migrates the (common) pattern into Guile proper, and exposes it
under a suitably coherent design.

Too many buzzwords, i know.  But i hope you understand anyway.

   Is there a way to do this that I don't know?

Only you know what you do not know, so who else can answer that?
Next question!  :-D

-- 
Thien-Thi Nguyen -----------------------------------------------
  (if you're human and you know it) read my lisp:
    (defun responsep (type via)
      (case type
        (technical (eq 'mailing-list via))
        ...))
---------------------------------------------- GPG key: 4C807502

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2015-04-15 21:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14  0:17 Pipes and processes, stdin, stdout and stderr Christopher Allan Webber
2015-04-14 16:41 ` Vladimir Zhbanov
2015-04-14 17:45   ` Christopher Allan Webber
2015-04-15 21:38 ` Thien-Thi Nguyen [this message]
2015-04-16 15:34   ` Christopher Allan Webber
2015-04-17 19:44     ` Thien-Thi Nguyen
2015-04-18 15:44 ` Mark H Weaver
2015-05-17 12:14   ` Pipes and processes, stdin, stdout and stderr -- ./configure in Guile Jan Nieuwenhuizen

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=87r3rlul4p.fsf@zigzag.favinet \
    --to=ttn@gnu.org \
    --cc=guile-user@gnu.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).