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: Mon, 20 Sep 2004 10:38:19 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Running cmd programs in cygwin / rxvt Message-ID: <20040920143819.GC6915@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <414E8B1A DOT 8040103 AT overbored DOT net> <414EA28E DOT 122EB347 AT dessent DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <414EA28E.122EB347@dessent.net> User-Agent: Mutt/1.4.1i On Mon, Sep 20, 2004 at 02:27:42AM -0700, Brian Dessent wrote: >overbored wrote: >>There are some cmd shell programs that don't run well in rxvt. Most >>noticeably, they don't always immediately write out their output. They >>seem to work fine in the default cmd window though (doesn't matter if >>it's in cmd or in bash). Does anybody know what the problem is here, >>and how to fix it? Thanks in advance. > >What you're seeing is caused by the output of the program going through >a tty (or pty as the case may be.) When you run it from a straight >cmd.exe it's not using tty code (unless you have CYGWIN=tty set.) From >my meagre knowledge of the subject it has to do with the program not >explicitly flushing stdout (or not knowing that it needs to as this is >usually not required under windows.) That's more or less correct. The larger problem is that ptys are actually pipes under the hood and some native programs don't deal well with having pipes for their stdin and stdout. They either don't flush their output correctly or they refuse to output anything at all. cgf -- 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/