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, 19 Mar 2003 12:34:09 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: RXVT Problem with buffering of application output. Message-ID: <20030319173409.GB24560@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <768A0EA6FF8CB34FA522978966E5D52E453743 AT bwam02msx DOT ae DOT ge DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <768A0EA6FF8CB34FA522978966E5D52E453743@bwam02msx.ae.ge.com> User-Agent: Mutt/1.5.1i On Wed, Mar 19, 2003 at 11:48:40AM -0500, Fletcher, Bob (GEAE, IT) wrote: > >A Few weeks ago ayamico at yahoo dot com posted a question about RXVT. I >haven't seen any response and was wondering if anyone else is having/looking at >this problem. > >The previous message is: >http://sources.redhat.com/ml/cygwin/2003-03/msg00524.html 2003-03-07, 4989 bytes > >When we run some commertial, native windows applications, we don't get >prompts written to standard out until the application ends. That's because cygwin's ptys are actually pipes. The native app doesn't know that this particular pipe is actually a pty (although a cygwin app would of course) and buffers its output as if the application was not being run interactively. The only alternative is to change the native app's buffering. cgf -- 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/