Date: Wed, 16 Nov 2005 14:07:18 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] Updated: lynx-2.8.5-4 Message-ID: <20051116130718.GR3462@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <267600-2200511316121950514 AT cantv DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <267600-2200511316121950514@cantv.net> User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 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, http://cygwin.com/acronyms/#WJFFM. Is your $TERM set to something weird? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc. -- 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/