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 Message-ID: <414EA28E.122EB347@dessent.net> Date: Mon, 20 Sep 2004 02:27:42 -0700 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Running cmd programs in cygwin / rxvt References: <414E8B1A DOT 8040103 AT overbored DOT net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com 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.) Brian -- 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/