From 536c6da6d1239c5dbc0e0b4e2e880db98b1f7f4b Mon Sep 17 00:00:00 2001 From: David Herrmann Date: Tue, 29 May 2012 12:46:09 +0200 Subject: [PATCH] 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 --- src/vte.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/vte.c b/src/vte.c index da3ea62..a421549 100644 --- a/src/vte.c +++ b/src/vte.c @@ -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; -- 2.7.4