út 16. 9. 2025 v 19:03 odesílatel Jakub Horký <[email protected]> napsal:
> But back to the poor app developer: so they must use keypad app mode > (otherwise the cursor keys won't work at all), even when only standard > numeric keypad functionality is needed, and have to implement all the > numeric keypad keys just to make the numeric keypad work. However, because > of overlapping caps, the developer can't decide which key was pressed, > because it might mean one key (if the terminal historically randomly > happens to use vt100+keypad building block) or another (if the terminal > historically randomly happens to use vt220+keypad building block). > Hello, I've assembled a table which maps the result of the ncurses function keyname() when a key is pressed in various terminals - i.e., WezTerm, xterm, xterm with sunKeyboard:true, PuTTY, mlterm, Tera Term, Konsole, Terminology, and Apple Terminal (nsterm). It clearly demonstrates the problems described. The table covers the most commonly used keyboards today (ISO and ANSI layouts in the most common variants - i.e., Windows and Mac). For now, the table only maps keys without modifiers. Cell color indicates whether the terminfo definition is correct or incorrect. https://jakub.horky.net/terminal/keyname.html Jakub
