X-Matched-Lists: []
Message-ID: <304070-2200511316173122210@cantv.net>
Reply-To: rodmedina AT cantv DOT net
From: "Rodrigo Medina" <rodmedina AT cantv DOT net>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] Updated: lynx-2.8.5-4
Date: Wed, 16 Nov 2005 13:31:22 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
X-Virus-Status: Clean
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

ON Nov 16 14:07 Corinna Vinschen  wrote:
>On Nov 16 08:19, Rodrigo Medina wrote:
>> Hi,
>> llynx has an extrange and bothering behavior, that actually is not
>> exclusive of this last version:
>> If you call lynx  from a command window, when it returns it leaves the
>> terminal in a starnge status with 
>> no  echo.  In order to  recover the proper behavior of the terminal one
has
>> to type (with no echo)
>> $ stty sane
>> I think that any program should  leave the terminal in its original
state.
>> bye,
>Is your $TERM set to something weird?

The same thing happens with RXVT ($TERM=xterm),  CMD ($TERM=cygwin) and
xterm ($TERM=term)
bye



--
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/