Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
To:	cygwin AT cygwin DOT com
X-Injected-Via-Gmane:	http://gmane.org/
Path:	not-for-mail
From:	Pietro Toniolo <ptoniolo AT tin DOT it>
Newsgroups:	gmane.os.cygwin
Subject:	Re: Strange behavior of MSVC's printf under cygwin shell?
Date:	Mon, 25 Mar 2002 23:02:36 +0100
Lines:	11
Message-ID:	<3C9F9E7C.EB74DC31@tin.it>
References:	<LAW2-OE53WO6hm8Ua8d000018b3 AT hotmail DOT com>
NNTP-Posting-Host:	213.140.15.170
Mime-Version:	1.0
X-Trace:	main.gmane.org 1017093757 17805 213.140.15.170 (25 Mar 2002 22:02:37 GMT)
X-Complaints-To:	usenet AT main DOT gmane DOT org
NNTP-Posting-Date:	Mon, 25 Mar 2002 22:02:37 +0000 (UTC)
X-Accept-Language:	en,it

Wirawan Purwanto wrote:

> Why does the screen output displayed using MSVC's printf subroutine not get
> shown immediately under Cygwin shell (bash, specifically)? Rather, it would
> wait for a long time before showing the text lines (many lines at once). How
> to change this behavior?

With -mno-cygwin, stdout is buffered. You can realize it if you put a
fflush(stdout) after the printf: the behavior is what you expect.

But, why this difference? I don't know.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -