Date: Thu, 27 May 2010 10:03:01 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygwin  : bash doesn't recognize BackSpace
Message-ID: <20100527140301.GC21583@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <4BFE4DF6.4080302@yandex.ru> <4BFE5B77.9050005@gmail.com> <4BFE7881.4050306@yandex.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4BFE7881.4050306@yandex.ru>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Thu, May 27, 2010 at 05:49:53PM +0400, Andrei Dmitriev wrote:
>Dave Korn wrote:
>>On 27/05/2010 11:48, Andrei Dmitriev wrote:
>>>after I installed the cygwin on May 19 the bash console don't recognize
>>>*********BACKSPACE***** and continue to follow to the right each time I
>>>press BACKSPACE.  Although, seem it actually erases the chars from the
>>>left (ENTER says nothing - so I concluded the command is empty).
>>>
>>
>>MKS tools are interfering with Cygwin, because of these environment
>>variable settings:
>>>
>>>TERM = 'nutc'
>>>TERMCAP = 'D:\PROGRA~1\MKSTOO~1\etc\termcap'
>>>TERMINFO = 'D:\PROGRA~1\MKSTOO~1\usr\lib\terminfo'
>>
>>You need to remove them from the environment, and should set your PATH
>>so it doesn't have both Cygwin and MKS at the same time.
>>
>Ok, I removed mks from my path but the problem persists.

It sounds like you only did half of what you need to.  You need to
remove the other environment variables too.  Setting TERM=nutc is
obviously incorrect for cygwin, as is pointing to non-cygwin vesions of
TERMCAP and TERMINFO.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple