diff options
author | nicm <nicm> | 2016-12-30 13:49:34 +0000 |
---|---|---|
committer | nicm <nicm> | 2016-12-30 13:49:34 +0000 |
commit | 1015b124d5ccb4c9d32f0c5aae820f7a1ac98c5c (patch) | |
tree | aa74bc8d7f2639ffb4c19e73a3d0154c35d449b8 | |
parent | 70ba3c147fffc86c9688ea7abf642d4fc92e692c (diff) | |
download | rtmux-1015b124d5ccb4c9d32f0c5aae820f7a1ac98c5c.tar.gz rtmux-1015b124d5ccb4c9d32f0c5aae820f7a1ac98c5c.tar.bz2 rtmux-1015b124d5ccb4c9d32f0c5aae820f7a1ac98c5c.zip |
Change the xterm-keys option to default to on, so that tmux will
generate xterm(1) escape sequences for function keys with modifiers.
With the option off most of these keys are ignored by default, except
for ctrl + arrows which use a variant that nothing else seems to use and
I don't remember why we chose. The xterm escape sequences are now the
most common.
Prompted by a question from mpi@.
-rw-r--r-- | options-table.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/options-table.c b/options-table.c index 5268d8b0..b63abaec 100644 --- a/options-table.c +++ b/options-table.c @@ -896,7 +896,7 @@ const struct options_table_entry options_table[] = { { .name = "xterm-keys", .type = OPTIONS_TABLE_FLAG, .scope = OPTIONS_TABLE_WINDOW, - .default_num = 0 + .default_num = 1 }, { .name = NULL } |