summaryrefslogtreecommitdiffstats
path: root/input-keys.c
AgeCommit message (Collapse)Author
2019-07-09Merge branch 'obsd-master'Thomas Adam
2019-07-09Add a -H flag to send-keys to send literal keys given as hex numbersnicm
(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.
2018-10-18Support for windows larger than visible on the attached client. This hasnicm
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.
2018-09-10Bring back window_pane_visible to stop input going to panes which areNicholas Marriott
hidden by zoom.
2018-08-20Support for windows larger than the client.Nicholas Marriott
This adds 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. 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). 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-width -x or -y. 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 higher memory use if you make a window that big. The minimum size is the size required for the current layout including borders. This change allows some code improvements, most notably that since windows can now never be cropped, that code can be removed from the layout code, and since panes can now never be outside the size of the window, window_pane_visible can be removed.
2017-06-28Merge branch 'obsd-master'Thomas Adam
2017-06-28Apply the xterm key flag when needed for send-keys, fixes problemnicm
reported by Franky Spamschleuder.
2017-06-12Merge branch 'obsd-master'Thomas Adam
2017-06-12Add explicit keys for the bracketed paste sequences, both to avoid mixnicm
ups with other keys and to make logs clearer.
2017-05-09Merge branch 'obsd-master'Thomas Adam
Conflicts: format.c
2017-05-07Up to now, tmux sees \033\033[OA as M-Up and since we turned onnicm
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.
2017-02-01Merge branch 'obsd-master'Thomas Adam
2017-02-01Implement "all event" (1003) mouse mode but in a way that works. Thenicm
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.
2017-01-25Revert previous for now, it will break TERM=screen.nicm
2017-01-25If xterm-keys is on, use xterm(1) style keys for Home and End as well asnicm
modified keys.
2016-10-04Merge branch 'obsd-master'Thomas Adam
2016-10-03Remove some dead code in cmd-move-window.c and make a load of localnicm
functions static.
2016-03-02Merge branch 'obsd-master'Thomas Adam
Conflicts: utf8.c
2016-03-02Limit x, y and b to 0x7ff for UTF-8 mouse input, suggested by schwarze@.nicm
2016-03-01Use system wcwidth() instead of carrying around UTF-8 width tables.nicm
2016-01-19Merge branch 'obsd-master'Thomas Adam
2016-01-19I no longer use my SourceForge address so replace it.nicm
2015-12-12Merge branch 'obsd-master'Thomas Adam
2015-12-12Allow prefix and prefix2 to be set to None to disable (useful if younicm
would rather bind the prefix in the root table).
2015-11-24Merge branch 'obsd-master'Thomas Adam
2015-11-23Partly revert previous, it is harmless to keep support for UTF-8 mousenicm
mode inside tmux, just no longer support it for tmux itself.
2015-11-23Merge branch 'obsd-master'Thomas Adam
2015-11-23Remove support for the UTF-8 mouse extension. This was a briefly used,nicm
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.
2015-11-17Merge branch 'obsd-master'Thomas Adam
2015-11-160x7f is a valid key.nicm
2015-11-14Merge branch 'obsd-master'Thomas Adam
2015-11-14All these return values from utf8_* are confusing, use an enum.nicm
2015-11-13Merge branch 'obsd-master'Thomas Adam
2015-11-12Rename overly-long utf8data to ud throughout.nicm
2015-11-12Merge branch 'obsd-master'Thomas Adam
2015-11-12Support UTF-8 key bindings by expanding the key type from int tonicm
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.)
2015-10-27Merge branch 'obsd-master'Thomas Adam
Conflicts: Makefile client.c server-client.c server.c tmux.c tmux.h
2015-10-27Move struct options into options.c.nicm
2015-10-26Merge branch 'obsd-master'Thomas Adam
2015-10-26Some extra logging of where keys are actually going.nicm
2015-04-22Merge branch 'obsd-master'Thomas Adam
2015-04-21Don't eat the mouse event that triggers a drag end because we may wantnicm
to pass it on to application inside the pane.
2015-04-20Merge branch 'obsd-master'Thomas Adam
2015-04-19Rewrite of tmux mouse support which was a mess. Instead of havingnicm
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.
2015-04-19Merge branch 'obsd-master'Thomas Adam
2015-03-31Fix some format specifier nits, from Ben Boeckel.nicm
2014-11-09Merge branch 'obsd-master'Thomas Adam
2014-11-08No need for $Id$ now.Nicholas Marriott
2014-11-05Tidy up mode-mouse check.nicm
2014-08-09Merge branch 'obsd-master'Thomas Adam
Conflicts: client.c