[9855] in Athena Bugs
Re: rt 7.4G: /etc/termcap
daemon@ATHENA.MIT.EDU (Calvin Clark)
Thu Sep 3 12:15:02 1992
Date: Thu, 3 Sep 92 12:14:46 -0400
From: Calvin Clark <ckclark@mit.edu>
To: John T Kohl <jtkohl@cs.berkeley.edu>
Cc: bug-x11r5@Athena.MIT.EDU, bugs@Athena.MIT.EDU
Reply-To: ckclark@mit.edu
>>>>> On Thu, 3 Sep 92 09:01:45 -0700, John T Kohl <jtkohl@cs.berkeley.edu> said:
>If you turn on "Enable Application Cursor Keys" from the xterm
>middle-button menu, the arrow keys do indeed generate \EOA ... \EOD.
>I believe there's an escape sequence you can send to xterms/vt100's
>which will turn on the application cursor mode.
I know about the ks and ke capabilities. However, on many terminals, it
is apparently not necessary to use them to turn "keypad transmit" mode
on/off before using the arrow key sequences.
The program in question is Elvis. From the Changes in the most recent
version (1.6):
- The :ks=:ke=: termcap strings aren't used anymore. Those strings are
supposed to be used to put the keypad in "application mode", but it seems
that editors aren't applications in the eyes of termcap entry writers.
The :ks=: string was making the arrow keys send goofy codes instead of the
normal codes defined in :ku=: etc.
So the arrow keys on a vt100 or Xterm are more likely to work now.
Of course, they are actually less likely to work. (By the way, the
vt100 entry has the same problem as the xterm entry.)
I am not sure what the last word is on whether or not you should have
to set the terminal in "application mode" or not before using arrow
keys. Termcap behavior has become a vaild "lore" topic. :-)
-Calvin
