Date: Fri, 18 Nov 2005 21:21:30 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: strange bash behavior with CYGWIN=tty (was Re: [ANNOUNCEMENT] Updated:  lynx-2.8.5-4)
Message-ID: <20051119022130.GB32402@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <12860-220051131621311591 AT cantv DOT net> <dlln37$201$1 AT sea DOT gmane DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <dlln37$201$1@sea.gmane.org>
User-Agent: Mutt/1.5.8i
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Fri, Nov 18, 2005 at 03:11:34PM -0800, Shankar Unni wrote:
>Rodrigo Medina wrote:
>
>>The cycheck output is attached.
>
>Can't see anything odd here. Of course, since you didn't use the '-v' 
>and '-r' options, I don't see your environment, or your registry 
>settings here.
>
>But while I was playing around with my own settings to try to reproduce 
>this (I normally don't set CYGWIN at all), I ran into something odd with 
>bash. (Didn't even get as far as starting lynx).
>
>Trying
>
>  env CYGWIN=tty bash
>
>gave me a bash in which the first command echoes properly, but the 
>second and subsequent commands don't echo at all.

Correct.  You need to set CYGWIN=tty before you start the first Cygwin
process.

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/