Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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:	<414EEDAB.B2852F85@dessent.net>
Date:	Mon, 20 Sep 2004 07:48:11 -0700
From:	Brian Dessent <brian AT dessent DOT net>
Organization:	My own little world...
MIME-Version:	1.0
CC:	cygwin AT cygwin DOT com
Subject:	Re: Running cmd programs in cygwin / rxvt
References:	<414E8B1A DOT 8040103 AT overbored DOT net> <414EA28E DOT 122EB347 AT dessent DOT net> <cimon4$783$1 AT sea DOT gmane DOT org>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

Andrew DeFaria wrote:

> > 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.)
> 
> Is there a CYGWIN setting to tell rxvt not to use ptys?

I don't think that would do any good.  rxvt is a posix program and
expects an environment where it has ptys that it can use.  Without pty
support it would likely complain loudly and refuse to run.

Again, I'm pontificating on something I know little about here, but I'm
guessing one solution might be some kind of kludge in the cygwin layer
that would attempt to detect when a native app is doing buffered writes
to a pty and autoflush after each call.  But, just a WAG.  It might even
be out of cygwin's control, if the buffering is done in the CRT of the
app.

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/

- Raw text -