Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <000601c4d226$c3c6c370$768010ac@wksh118> From: "Fekete Krisztian" To: References: <000501c4d174$81c688a0$768010ac AT wksh118> <20041123161048 DOT GA9142 AT trixie DOT casa DOT cgf DOT cx> Subject: Re: Sequential writes to stdout is messed up (Bash only?) Date: Wed, 24 Nov 2004 14:08:55 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Yes, the test version bash 2.05b-17 seams to solve the problem. Thanks! BTW the one liner to demonstrate the problem was not correct (http://cygwin.com/ml/cygwin/2004-11/msg00946.html). The correct one is: printf 1 > 1; while true; do cat 1; echo 2; done | cat The difference is the "| cat" without which the correct 12 sequence is generated. You need to have a pipe to get the bad output. ----- Original Message ----- From: "Christopher Faylor" To: Sent: Tuesday, November 23, 2004 5:10 PM Subject: Re: Sequential writes to stdout is messed up (Bash only?) > On Tue, Nov 23, 2004 at 04:52:57PM +0100, Fekete Krisztian wrote: > >The problem can be demonstrated by executing the following in bash: > > You probably want to try the recently announced test version of bash: > > http://cygwin.com/ml/cygwin-announce/2004-11/msg00024.html > -- 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/