Steve Isard wrote:
I think I have encountered the problem that led Aaron to disable the use of
termcap in linux in 2003.
Of which I have no memory at all! (Brain steadily going downhill now.)
.... Non-x ved now starts up for terminals known to
terminfo, and I can get around using control keys, but keys that generate
sequences of characters - e.g., arrow keys and function keys - aren't
working.
Are they not generating anything, or generating the wrong sequences?
You may already know this but you can find out what sequences are produced
by doing this in Ved (or xved)
ENTER inkeys
It prints out on command line:
TO TERMINATE PRESS ESCAPE button THREE TIMES
I pressed keypad buttons 1 2 3 then esc esc esc, and ved inserted this:
\^[[FF9C\^[[FF99\^[[FF9B
(I leave you to translate that to ascii: '\^[[' = ESC)
I _think_ the problem is that vedescapetable is not being populated
correctly. My uparrow key generates the sequence esc [ A, ascii 27 91 65.
Mine does (with inkeys): \^[[FF9C\^[[FF99\^[[FF9
I've discovered that in Fedora 32 with $TERM set to xterm, the
keypad Ins and Del now insert
\^[[FF9E \^[[FF9F
different from earlier versions of fedora.
\^[Op \^[On
So I had to alter my key preferences to make those keys do Wordleft and
Wordright as in the past. I am very surprised at something like that
changing between versions of Fedora. I presume the change does not come
from poplog.
When I have TERM set to xterm, vedescapetable(91) has a subsequence '65
vedcharup'. When TERM is set to rxvt-unicode or some other vt100 superset
that doesn't have its own poplog definitions, vedescapetable(91) does not
have the number 65 anywhere in it.
I haven't yet understood how vedescapetable gets its values. The file
vedtermcap.p looks relevant, but is not easy to follow.
Try $usepop/pop/ved/src/vdkeys.p
search for newescapetable oldescapetable ??
====
Sorry I can't be more specific.
Aaron
