Bug 80475 – Arrow keys do not work in vi (vim) with numlock on

Bug 80475 - Arrow keys do not work in vi (vim) with numlock on

Summary:	Arrow keys do not work in vi (vim) with numlock on

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	vim (Show other bugs)
Sub Component:
Version:	9
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Karsten Hopp
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-12-26 19:57 EST by Forrest
Modified:	2007-04-18 12:49 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-08-26 16:30:29 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Forrest 2002-12-26 19:57:56 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218

Description of problem:
The arrow keys do no work in vi (vim) when the numlock is on.  I get:
E388: Couldn't find definitions

When the numlock is off, the arrow keys work as expected.


Version-Release number of selected component (if applicable):
6.1-17

How reproducible:
Always

Steps to Reproduce:
1.  From terminal, start vi
2.  Enter some text (if it is a new file), or verify that the arrow keys work
3.  Turn on the numlock key, and try to use the arrow keys.
    

Actual Results:  E388: Couldn't find definitions

Comment 1 Need Real Name 2003-01-27 10:20:14 EST

I get the same problem. Thanks for including the workaround.

Comment 2 Josiah Royse 2003-01-27 14:34:50 EST

I also experienced this in Phoebe1, but the second Phoebe beta 8.0.93 it works:
version vim-*-6.1-23

Note You need to log in before you can comment on or make changes to this bug.