| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
use these key sequences by default. Merge the code into the main tty and input
tree processing (convering the latter to use a tree rather than a table at the
same time) and make the option a no-op.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
xterm-keys by default, generates \033[1;3A instead of
\033\033[OA. Unfortunately this confuses vi, which doesn't understand
xterm keys and now sees Escape+Up pressed within escape-time as Escape
followed by A.
The issue doesn't happen in xterm itself because it gets the keys from X
and can distinguish between a genuine M-Up and Escape+Up.
Because xterm can, tmux can too: xterm will give us \033[1;3A (that is,
kUP3) for a real M-Up and \033\033OA for Escape+Up - in fact, we can be
sure any \033 preceding an xterm key is a real Escape key press because
Meta would be part of the xterm key instead of a separate \033.
So change tmux to recognise both sequences as M-Up for its own purposes,
but generate the xterm version of M-Up only if it originally received
the xterm version from the terminal.
This means we will return to sending \033\033OA instead of the xterm key
for terminals that do not support xterm keys themselves, but there is no
practical way around this because they do not allow us to distinguish
between Escape+Up and M-Up. xterm style escape sequences are now the de
facto standard for these keys in any case.
Problem reported by jsing@ and subsequently by Cecile Tonglet in GitHub
issue 907.
|
| | |
|
| |
|
|
| |
modified keys.
|
| |
|
|
| |
functions static.
|
| | |
|
| |
|
|
|
|
| |
uint64_t and converting UTF-8 to Unicode on input and the reverse on
output. (This allows key bindings, there are still omissions - the
largest being that the various prompts do not accept UTF-8.)
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
entry:
F13-F24 are S-F1 to S-F12
F25-F36 are C-F1 to C-F12
F37-F48 are C-S-F1 to C-S-F12
F49-F60 are M-F1 to M-F12
and F61-F63 are M-S-F1 to M-S-F3
This should be no difference for applications inside tmux, but means
that any key binding for F13 will need to be replaced by S-F1 and so on.
|
| |
|
|
| |
Balazs Kezes.
|
| |
|
|
|
|
| |
being wrongly treated as partial matches. So both check xterm keys after
standard keys and only wildcard the minimum required ('1' to
'8'). Problems reported by Ralf Horstmann and Tim van der Molen.
|
| |
|
|
| |
googlemail dot com.
|
| |
|
|
| |
and handle the most common set. Pass them through if xterm-keys is on.
|
| |
|
|
| |
from Dustin Kirkland.
|
| |
|
|
|
| |
xterm-style keys - bit 3 is accepted on input but not on output. Also a
style nit in the header.
|
| | |
|
| |
|
|
| |
escape (tmux's meta). From Emanuele Giaquinta.
|
| |
|
|
| |
by and diff from Emanuele Giaquinta.
|
| |
|
|
|
| |
time now I've configured emacs to make them displayed in really annoying
colours...
|
| | |
|
| | |
|
| | |
|
|
|
output the same modifiers, accepts all the possible input keys) and is more
understandable.
|
