This is the mail archive of the
mailing list for the Cygwin project.
Re: 1.7.35: possible backspace key and arrow keys bug
- From: Weston Turner <wstnturner at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 9 Apr 2015 09:54:59 -0700
- Subject: Re: 1.7.35: possible backspace key and arrow keys bug
- Authentication-results: sourceware.org; auth=none
- References: <CAMOkCRZ4Tdg+UoydTj+ntXyyFvbhk8ug6A+LXAG3+zOw4UfuTw at mail dot gmail dot com> <20150408221622 dot GK20741 at dinwoodie dot org>
I corroborate the original poster's experience with this issue.
Steps to reproduce the issue: for example open a file with vim under
Cygwin, press: up, up, down, down, left, left, right, right. Vim under
in the file due to the arrow keys being pressed. Vim under bash on
Linux or the Mac terminal does not treat the arrow keys as file input,
but rather simply uses them to move the cursor about in the file.
On Wed, Apr 8, 2015 at 3:16 PM, Adam Dinwoodie <email@example.com> wrote:
> On Wed, Apr 08, 2015 at 09:42:55PM +0800, George jiang wrote:
>> I am using a thinkpad laptop preinstalled win8 system, later
>> upgraded to win8.1. I installed the latest version of cygwin, found
>> when using vim editor can not backspace to delete characters, press
>> the arrow keys appear 'A', 'B' and other characters. I follow the
>> online presentation solutions, copied from a vimrc_example.vim ubentu
>> system files to / home / xx folder and renamed .vimrc, the results
>> still does not work. I ask this is a bug it? Please help.
> You've really not given us much to go on here. For a start, it would be
> really useful if you could read the problem reporting guidelines at the
> link below, which will point you at the various bits of information that
> we'd need to be able to work out what's going on.
>> Problem reports: http://cygwin.com/problems.html
> In particular, we need exact step-by-step instructions of what you're
> doing, the behaviour you're seeing, and how that differs from the
> behaviour you'd expect to see. That way we can tell you whether what's
> happening is a bug or not, and if it is a bug, we'll be able to do the
> same things ourselves so we can see exactly where the bug is to fix it.
> 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
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple