X-Spam-Check-By: sourceware.org
Message-ID: <ba40711f0706070704w3486145cr17a1fd82f8132bfa@mail.gmail.com>
Date: Thu, 7 Jun 2007 10:04:26 -0400
From: "Lev Bishop" <lev DOT bishop AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] New package: brltty 3.8
In-Reply-To: <20070607122642.GA31803@trixie.casa.cgf.cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20070606102654 DOT GA11636 AT calimero DOT vinschen DOT de> 	 <announce DOT 20070605230831 DOT GC3356 AT implementation> 	 <f45rfu$r9r$1 AT sea DOT gmane DOT org> <20070606085100 DOT GA5082 AT implementation> 	 <4666819A DOT 52A6488D AT dessent DOT net> <20070606192445 DOT GG6500 AT implementation> 	 <20070606201111 DOT GA2366 AT ednor DOT casa1 DOT cgf DOT cx> 	 <20070607114950 DOT GA3958 AT implementation> 	 <20070607122642 DOT GA31803 AT trixie DOT casa DOT cgf DOT cx>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 6/7/07, Christopher Faylor wrote:
> On Thu, Jun 07, 2007 at 07:49:50PM +0800, Samuel Thibault wrote:
<snip>

> >But when talking about communicating with other applications, we need to
> >use windows interfaces when the linux API doesn't permit it, shouldn't
> >we?
>
> Only if you can clearly communicate why the linux API doesn't work.  I'm
> not convinced that this is not just a misconception on your part.

Or to put it another way -- cygwin is rather careful when it comes to
pipes to make sure that all of these uses work correctly and
interoperate with with windows:

C:\>dir | less
C:\>ls | less
C:\>dir | \windows\system32\more.com
C:\>ls | \windows\system32\more.com
$ cmd /c dir | les
$ ls | less
$ cmd /c dir | /cygdrive/c/windows/system32/more.com
$ cmd /c dir | /cygdrive/c/windows/system32/more.com

(ie all 8 combinations of pipe-created-by:{win,cygwin},
source:{win,cygwin}, sink:{win,cygwin} )

So, the big question is: what does brltty do with pipes that is
different to the above?

I know there are certain potential problems with non-blocking I/O on
pipes on cygwin, but they are limited to quite specific cases (rsync
is the main one that trips over this).

Lev

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/