DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=CE9SM0cNqAJ3YZjp
	czNXp+urjkKJiC8ZPz97lP/K0X4Af9zafFmMvujMuLnV70BgL4d1QhHVZt9kQjaI
	kPdO5DUwUHu/FB5NurDo04Whwsfm2dLX7q+fOYSYOG8IEQoV8YIuT9Li8T5ksUck
	kVfTAYHrk6kF1gyqCSJfSBHStBk=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Reply-To: moss@cs.umass.edu
Subject: Re: pipe broken by WSL?
To: cygwin@cygwin.com
References: <2a6d7c3d-f8ff-eafe-3048-8bbd689216c5@towo.net> <20190502153726.GA1867@zebra>
From: Eliot Moss <moss@cs.umass.edu>
Message-ID: <a2cc9af3-eb31-8b7d-e3f4-fa3e2f21cd40@cs.umass.edu>
Date: Thu, 2 May 2019 12:26:18 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <20190502153726.GA1867@zebra>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

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.

Regards - Eliot

--
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