DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=kl2UNNnTaWt08mtS
	snUK5dOESrEbSxs3wtQbK4kCnjOIdS4zCwFpLx+1y5t6uqRZTpNeO2Ue6uNOsw/h
	1TVNSilpNug5A5rXum7jmuaXNwZvOCWGTwN236/Zy/dkI5/lGIqrMJdnd83MIGU+
	I75EbMR4R6J95Rj7kBd2gsby+vM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 3 May 2019 21:52:25 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <473270892.20190503215225@yandex.ru>
To: Eliot Moss <moss@cs.umass.edu>, cygwin@cygwin.com
Subject: Re: pipe broken by WSL?
In-Reply-To: <a2cc9af3-eb31-8b7d-e3f4-fa3e2f21cd40@cs.umass.edu>
References: <2a6d7c3d-f8ff-eafe-3048-8bbd689216c5@towo.net> <20190502153726.GA1867@zebra>   <a2cc9af3-eb31-8b7d-e3f4-fa3e2f21cd40@cs.umass.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Greetings, Eliot Moss!

> On 5/2/2019 11:37 AM, Stephen Carrier wrote:
>> On Wed, May 01, 2019 at 11:20:59AM +0200, Thomas Wolff wrote:
>>> Calling WSL seems to break pipe processing:
>>>
>>> (echo 1; echo 2) |
>>> while read line
>>> do
>>>    echo $line
>>>    wsl uname
>>> done
>> 
>> I don't know about wsl, but could it be absorbing the standard input?
>> What if "wsl uname" is replaced with "wsl uname < /dev/null" ?

> You seem to be right; when I add < /dev/null as described, I get
> the expected output.

Why not just

    wsl uname <&-

I wonder?


-- 
With best regards,
Andrey Repin
Friday, May 3, 2019 21:51:38

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