On Sun, Nov 08, 2015 at 04:50:21PM +0000, Nicholas Marriott wrote:
Can you please send these upstream to Thomas Dickey or
bug-ncur...@gnu.org?
Done.
* Add a new entry, 'pcconX', that adds F13-F24 to the standrd xterm entry
Not this though - pccon* is for the console, not for use in xterm. I
think you might want xterm-vt220?
Hummmm, no, xterm-vt220 doesn't define F21-F24, and also has an incorrect
definition for the, 'home', key.
I can make a diff for this, obviously, should I just add it as a variation?
Although I don't know why our xterm function keys should be different
from stock xterm.
Since F13-F24 don't exist on standard PC keyboards, traditionally terminal
emulators have mapped shift-F1 to F13, shift-F2 to F14, etc.
In recent times, some 122-key terminal keyboards, which are designed to be used
with terminal emulators like that, actually send sequences such as Shift-F1
when the physical F13 key is pressed, instead of the, 'real', sequence.
If you look in xterm+pcf2, which is the fragment included in the default xterm
terminfo entry that we use, you'll see that F13-F24 are indeed defined as
Shift-F1 - Shift-F12.
Unfortunately, even this doesn't work correctly for us, because F1-F4 don't
follow the normal sequence for historical reasons.
So, we should do something to make sure that the default terminal emulation
used for xterm on a default install, has a sensible configuration for F13-F24.
Either support the, 'real', sequences from a 122-key keyboard, or support the
shifted F1-F12 keys as F13-F24, or preferably, both.
Shall I make a diff to fix this?
--
Tati Chevron
Perl and FORTRAN specialist.
SWABSIT development and migration department.
http://www.swabsit.com
