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 Date: Wed, 5 Mar 2003 09:20:58 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Cc: cygwin AT cygwin DOT com Subject: Re: Strange bash behaviour Message-ID: <20030305142058.GB24337@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com, cygwin AT cygwin DOT com References: <200303051113 DOT 10638 DOT malcolm DOT agnew AT t-online DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200303051113.10638.malcolm.agnew@t-online.de> User-Agent: Mutt/1.5.1i Wrong mailing list. Redirected. On Wed, Mar 05, 2003 at 11:13:10AM +0100, Malcolm Agnew wrote: >Consider the program: > >int main( int argc, char **argv ) >{ > printf( "Hello\n" ) ; > printf( ">> " ) ; > getchar() ; >} >On compiling this with gcc the behaviour is as expected. i.e. >% foo >Hello >>> [wait for input] >But compiling with Visual C produces some strange results. >1. In an MSDOS window the behaviour is as expected. >2. In a bash window the two printf's do not get flushed even after hitting any >key plus return. >3. Older versions of cygwin work as expected. > >Malcolm -- 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/