Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: cygwin@cygwin.com X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: Pietro Toniolo 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: NNTP-Posting-Host: 213.140.15.170 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1017093757 17805 213.140.15.170 (25 Mar 2002 22:02:37 GMT) X-Complaints-To: usenet@main.gmane.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/