vte: handle XK_Find and XK_Select
Even though modern keyboard often do not include such keys, we should handle them correctly, anyway. For the sake of backwards-compatibility. This also comes in handy if you define these keys separately. The functions that are implemented by many applications with these keys are handy, indeed. Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
This commit is contained in:
parent
30c1c20876
commit
536c6da6d1
@ -1348,12 +1348,18 @@ void kmscon_vte_handle_keyboard(struct kmscon_vte *vte,
|
||||
else
|
||||
vte_write(vte, "\x0d", 1);
|
||||
return;
|
||||
case XK_Find:
|
||||
vte_write(vte, "\e[1~", 4);
|
||||
return;
|
||||
case XK_Insert:
|
||||
vte_write(vte, "\e[2~", 4);
|
||||
return;
|
||||
case XK_Delete:
|
||||
vte_write(vte, "\e[3~", 4);
|
||||
return;
|
||||
case XK_Select:
|
||||
vte_write(vte, "\e[4~", 4);
|
||||
return;
|
||||
case XK_Page_Up:
|
||||
vte_write(vte, "\e[5~", 4);
|
||||
return;
|
||||
|
Loading…
x
Reference in New Issue
Block a user