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 Date: Tue, 10 May 2005 19:25:38 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer] Message-ID: <20050510172538.GP3375@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <051020051547 DOT 6892 DOT 4280D77E000CE20C00001AEC22007503300A050E040D0C079D0A AT comcast DOT net> <20050510164727 DOT GO3375 AT calimero DOT vinschen DOT de> <4280ECE7 DOT 3000609 AT etr-usa DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4280ECE7.3000609@etr-usa.com> User-Agent: Mutt/1.4.2i On May 10 11:18, Warren Young wrote: > Corinna Vinschen wrote: > > >Can anybody tell me what the `stty erase' setting is good for in > >/etc/profile? I'm using tcsh, so I'm not bothered by this stuff... > > This is fine as long are you're within your shell, or another program > that is tolerant of the two different ways of saying 'backspace'. > > If your 'erase' stty variable isn't set correctly, a number of things > fail to deal with backspace correctly. For just one example, password > entry when ssh'ing to another machine requires a correct 'erase' setting. Yes. Did you notice what I said? It's set automatically correctly for rxvt and the cygwin console and xterm if you *don't* touch it in /etc/profile. Can we stop this discussion and just do it right in /etc/profile by just not setting it? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto: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/