vi down arrow key not working

artjaniger · June 27, 2003, 11:02am

i am using windows nt hummingbird 7.0 host explorer telnet emulation. I have two connections to two different unix machines.
on one, the down arrow works fine in vi (it woks like the j option
on the other it looks like it is giving me a new line above
(like option O) and inserting a letter "B";
Both sessions yield "term=vt220" when i issue the :se command.
Both yield "vt220" when i echo $TERM outside of vi.
The first one is a HP-UX machine and the second one is a SunOs
machine

RTM · June 27, 2003, 11:22am

When in insert mode in vi, you can't use the up and down arrows or you will get exactly what you mentioned. You have to hit the Esc key, and then use the arrows.

Opps, never mind - I see what you mean. HP is does allow you to move around.

Checked on Sunsolve - it's been this way for a very long time - and from reading the following from Sunsolve, I doubt they are going to change it.

Customer complaint

The arrow keys do not function correctly while in type-over mode (type-over
mode
is entered by typing a capital R). If an arrow key is pressed while in
type-over mode vi will exit type-over mode, returning to command mode.

They are concerned that their user's (who are not experienced
computer users) will press an arrow key while in type-over mode, continue
typing, and the keys typed will be interpeted by the vi command interpeter,
allowing for the possible descruction of data. Example:
- The user enters type-over mode by typing a R.
- The user types a string of characters then presses an arrow key.
- The user does not realize that they are no longer in type-over mode
  and continues to type.
- If the user types something such as "dd" they will delete the line
  that the cursor is on.
- Since the users are not experienced computer users $they are 
  data entry operators$ they may not realize what has occured 
  and will continue editing the data, then save the file, thus
  corrupting the data file.

Work Around

RTM · June 27, 2003, 11:40am

Another interesting behavior -

Customer complaint

So if you use dtterm, you can get that function - but only if your TERM variable is set to dtterm.