aboutsummaryrefslogtreecommitdiff
path: root/input-keys.c
Commit message (Collapse)AuthorAge
* Remove stray spaces after function names.nicm2021-08-20
|
* Remove old shift function keys which interfere with xterm keys now.nicm2021-06-10
| | | | GitHub issue 2696.
* Move "special" keys into the Unicode PUA rather than making them top bitnicm2021-06-10
| | | | | set, some compilers do not allow enums that are larger than int. GitHub issue 2673.
* Change a type to fix a warning with some compilers.nicm2021-04-09
|
* Log the key written to the terminal as well as tmux's idea of what itnicm2021-04-08
| | | | is.
* Log missing keys when extended keys is on rather than fatal().nicm2020-11-17
|
* Some other warnings, GitHub issue 2382.nicm2020-09-18
|
* Try without cursor/keypad flags if a key doesn't exist, and limit ctrlnicm2020-06-01
| | | | key translation to ASCII keys. Fixes send-keys, GitHub issue 2247.
* Use the internal representation for UTF-8 keys instead of wchar_t andnicm2020-05-25
| | | | drop some code only needed for that.
* Some other ctrl keys need to be translated with extended keys on.nicm2020-05-19
|
* Add a terminal feature for enable/disable extended keys (supported bynicm2020-05-16
| | | | | | | xterm and mintty) and add an option to make tmux send it. Only forward extended keys if the application has requested them, even though we use the CSI u sequence and xterm uses CSI 27 ~ - this is what mintty does as well.
* Do not send mouse events if the program has not requested them.nicm2020-04-07
|
* Support mouse in popups.nicm2020-04-01
|
* Change input path so it doesn't require a pane.nicm2020-03-19
|
* Send mouse down event immediately rather than waiting for double clicknicm2020-03-16
| | | | | to finish which would now mean it was out of order. Reported by Mark Kelly.
* Treat plausible but invalid keys (like C-BSpace) as literal like anynicm2020-01-13
| | | | | other unrecognised string passed to send-keys. Reported by Anthony Sottile in GitHub issue 2049.
* Keep modifiers on backspace when translating it.nicm2019-11-18
|
* Add an option to set the key sent by backspace for those whose systemnicm2019-11-14
| | | | uses ^H rather than ^?. GitHub issue 1969.
* Add a -H flag to send-keys to send literal keys given as hex numbersnicm2019-07-09
| | | | | | (needed for control clients to send mouse sequences). Also add some format flags for UTF-8 and SGR mouse mode. Requested by Bradley Smith in GitHub issues 1832 and 1833.
* Support for windows larger than visible on the attached client. This hasnicm2018-10-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | been a limitation for a long time. There are two new options, window-size and default-size, and a new command, resize-window. The force-width and force-height options and the session_width and session_height formats have been removed. The new window-size option tells tmux how to work out the size of windows: largest means it picks the size of the largest session, smallest the smallest session (similar to the old behaviour) and manual means that it does not automatically resize windows. The default is currently largest but this may change. aggressive-resize modifies the choice of session for largest and smallest as it did before. If a window is in a session attached to a client that is too small, only part of the window is shown. tmux attempts to keep the cursor visible, so the part of the window displayed is changed as the cursor moves (with a small delay, to try and avoid excess redrawing when applications redraw status lines or similar that are not currently visible). The offset of the visible portion of the window is shown in status-right. Drawing windows which are larger than the client is not as efficient as those which fit, particularly when the cursor moves, so it is recommended to avoid using this on slow machines or networks (set window-size to smallest or manual). The resize-window command can be used to resize a window manually. If it is used, the window-size option is automatically set to manual for the window (undo this with "setw -u window-size"). resize-window works in a similar way to resize-pane (-U -D -L -R -x -y flags) but also has -a and -A flags. -a sets the window to the size of the smallest client (what it would be if window-size was smallest) and -A the largest. For the same behaviour as force-width or force-height, use resize-window -x or -y, and "setw -u window-size" to revert to automatic sizing.. If the global window-size option is set to manual, the default-size option is used for new windows. If -x or -y is used with new-session, that sets the default-size option for the new session. The maximum size of a window is 10000x10000. But expect applications to complain and much higher memory use if making a window excessively big. The minimum size is the size required for the current layout including borders. The refresh-client command can be used to pan around a window, -U -D -L -R moves up, down, left or right and -c returns to automatic cursor tracking. The position is reset when the current window is changed.
* Apply the xterm key flag when needed for send-keys, fixes problemnicm2017-06-28
| | | | reported by Franky Spamschleuder.
* Add explicit keys for the bracketed paste sequences, both to avoid mixnicm2017-06-12
| | | | ups with other keys and to make logs clearer.
* Up to now, tmux sees \033\033[OA as M-Up and since we turned onnicm2017-05-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Implement "all event" (1003) mouse mode but in a way that works. Thenicm2017-02-01
| | | | | | | | | | | main issue is that if we have two panes, A with 1002 and B with 1003, we need to set 1003 outside tmux in order to get all the mouse events, but then we need to suppress the ones that pane A doesn't want. This is easy in SGR mouse mode, because buttons == 3 is only used for movement events (for other events the trailing m/M marks a release instead), but in normal mouse mode we can't tell so easily. So for that, look at the previous event instead - if it is drag+release as well, then the current event is a movement event.
* Revert previous for now, it will break TERM=screen.nicm2017-01-25
|
* If xterm-keys is on, use xterm(1) style keys for Home and End as well asnicm2017-01-25
| | | | modified keys.
* Remove some dead code in cmd-move-window.c and make a load of localnicm2016-10-03
| | | | functions static.
* Limit x, y and b to 0x7ff for UTF-8 mouse input, suggested by schwarze@.nicm2016-03-02
|
* Use system wcwidth() instead of carrying around UTF-8 width tables.nicm2016-03-01
|
* I no longer use my SourceForge address so replace it.nicm2016-01-19
|
* Allow prefix and prefix2 to be set to None to disable (useful if younicm2015-12-12
| | | | would rather bind the prefix in the root table).
* Partly revert previous, it is harmless to keep support for UTF-8 mousenicm2015-11-23
| | | | mode inside tmux, just no longer support it for tmux itself.
* Remove support for the UTF-8 mouse extension. This was a briefly used,nicm2015-11-23
| | | | | | | | poor idea that was fairly quickly replaced by SGR mouse input (which is now widespread). It is impossible to tell the difference between UTF-8 and non-UTF-8 mouse input; since the mouse-utf8 option was removed tmux has not handled it correctly in any case; and it is ridiculous to have three different forms of mouse input.
* 0x7f is a valid key.nicm2015-11-16
|
* All these return values from utf8_* are confusing, use an enum.nicm2015-11-14
|
* Rename overly-long utf8data to ud throughout.nicm2015-11-12
|
* Support UTF-8 key bindings by expanding the key type from int tonicm2015-11-12
| | | | | | 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.)
* Move struct options into options.c.nicm2015-10-27
|
* Some extra logging of where keys are actually going.nicm2015-10-26
|
* Don't eat the mouse event that triggers a drag end because we may wantnicm2015-04-21
| | | | to pass it on to application inside the pane.
* Rewrite of tmux mouse support which was a mess. Instead of havingnicm2015-04-19
| | | | | | | | | | | | | | | | | | | | | | | | | options for "mouse-this" and "mouse-that", mouse events may be bound as keys and there is one option "mouse" that turns on mouse support entirely (set -g mouse on). See the new MOUSE SUPPORT section of the man page for description of the key names and new flags (-t= to specify the pane or window under mouse as a target, and send-keys -M to pass through a mouse event). The default builtin bindings for the mouse are: bind -n MouseDown1Pane select-pane -t=; send-keys -M bind -n MouseDown1Status select-window -t= bind -n MouseDrag1Pane copy-mode -M bind -n MouseDrag1Border resize-pane -M To get the effect of turning mode-mouse off, do: unbind -n MouseDrag1Pane unbind -temacs-copy MouseDrag1Pane The old mouse options are now gone, set-option -q may be used to suppress warnings if mixing configuration files.
* Fix some format specifier nits, from Ben Boeckel.nicm2015-03-31
|
* Tidy up mode-mouse check.nicm2014-11-05
|
* Revert the up/down wheel emulation for now, there will be a better waynicm2014-07-21
| | | | to do this along later for those who want it.
* Drop explicit support for F13-F20 and change to match the xterm terminfonicm2014-07-21
| | | | | | | | | | | | | 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.
* Send up and down keys for mouse wheel in alternate screen mode (when itnicm2014-05-08
| | | | normally does nothing), from Marcel Partap.
* There is no longer a need for a paste_stack struct or for global_buffersnicm2014-04-24
| | | | to be global. Move to paste.c.
* A couple of trivial mouse-related style nits.nicm2014-04-03
|
* Remove log_debug2 as well and simplify log.c.nicm2014-03-31
|
* Don't limit width and height to 222 in standard mouse mode.Nicholas Marriott2013-05-07
|
generated by cgit (git 2.34.1) at 2025-04-28 20:58:55 +0000