caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Matthew Hannigan <mlh@zip.com.au>
To: Matt Gushee <matt@gushee.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] LablGTK2: problem w/ GMain.Io
Date: Fri, 12 May 2006 09:13:31 +1000	[thread overview]
Message-ID: <20060511231331.GB23533@evofed.localdomain> (raw)
In-Reply-To: <4463B51F.6080807@gushee.net>

On Thu, May 11, 2006 at 04:05:19PM -0600, Matt Gushee wrote:
> 
>   echo '%show' > /tmp/bantam-matt/message.pipe
> 
> ) --this caused the I/O error. Yet, if invoked the same 'echo' command 
> directly in an interactive shell (in this case, bash running in an 
> rxvt), it never caused the error. Why on earth would that be, I wonder?

At a guess because stdin is a tty, then output might be line buffered
(regardless of destination?) 




      reply	other threads:[~2006-05-11 23:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-07 19:12 Matt Gushee
2006-05-08 18:25 ` [Caml-list] " Olivier Andrieu
2006-05-11 22:05   ` Matt Gushee
2006-05-11 23:13     ` Matthew Hannigan [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060511231331.GB23533@evofed.localdomain \
    --to=mlh@zip.com.au \
    --cc=caml-list@inria.fr \
    --cc=matt@gushee.net \
    /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 NNTP newsgroup(s).