DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:date:to:subject:message-id:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; q=dns; s=default; b=c8Z0YpLufEZwFZ7RbQwNCineP6ptXP
	Z8171qQt4+KwsVefROfSwnuGv69CzaAEd++OonZxKPHtw0dkd4lSKNkLMEXwvaHd
	xZEyVxxrC4jfDhNCshrwYZZpMeNyc6MeoD2R3r+lH3+dj95E6zQ/JU3HxwtCSlOG
	keHbcAYXYdCtg=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Stephen Carrier <carrier@berkeley.edu>
Date: Thu, 2 May 2019 08:37:26 -0700
To: cygwin@cygwin.com
Subject: Re: pipe broken by WSL?
Message-ID: <20190502153726.GA1867@zebra>
References: <2a6d7c3d-f8ff-eafe-3048-8bbd689216c5@towo.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <2a6d7c3d-f8ff-eafe-3048-8bbd689216c5@towo.net>
User-Agent: Mutt/1.9.1 (2017-09-22)

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

Stephen Carrier
BEAR Center

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