| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
the most reasonable of the various (some bizarre) suggestions for
capabilities.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
some modern features.
Now the common code is in mode-tree.c, which provides an API used by the
three modes now separated into window-{buffer,client,tree}.c. Buffer
mode shows buffers, client mode clients and tree mode a tree of
sessions, windows and panes.
Each mode has a common set of key bindings plus a few that are specific
to the mode. Other changes are:
- each mode has a preview pane: for buffers this is the buffer content
(very useful), for others it is a preview of the pane;
- items may be sorted in different ways ('O' key);
- multiple items may be tagged and an operation applied to all of them
(for example, to delete multiple buffers at once);
- in tree mode a command may be run on the selected item (session,
window, pane) or on tagged items (key ':');
- displayed items may be filtered in tree mode by using a format (this
is used to implement find-window) (key 'f');
- the custom format (-F) for the display is no longer available;
- shortcut keys change from 0-9, a-z, A-Z which was always a bit weird
with keys used for other uses to 0-9, M-a to M-z.
Now that the code is simpler, other improvements will come later.
Primary key bindings for each mode are documented under the commands in
the man page (choose-buffer, choose-client, choose-tree).
Parts written by Thomas Adam.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
adjusting the selection, it should never have any useful history (and
when it does, after resize, we shouldn't use it). From Michal Mazurek.
|
| |
|
|
|
|
| |
"bertnp" in GitHub issue 942.
|
|
|
|
|
| |
80x24 and the status line is not applied until they attach. Also make -x
and -y work for control clients whether the session is detached or not.
|
|
|
|
| |
issue 947.
|
| |
|
| |
|
|
|
|
|
|
| |
it is present and zero. This is useful for users with terminals or fonts
that do not correctly support UTF-8 line drawing characters. GitHub
issue 927, reported by Hiroaki Yamazoe and Akinori Hattori.
|
| |
|
|
|
|
|
|
| |
ignores if >= size, not if > as I first thought). So we can't
effectively fix it in code - remove the workarounds which just cause
bugs on other terminals.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
background colour - there may be portions that we do not want to clear
with the new background colour.
|
| |
|
|
|
|
| |
column 0, some do not).
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
are supported.
|
| |
|
|
|
|
|
| |
if you exit and reenter copy mode (it doesn't remember the position,
just the search string), suggested by espie@.
|
| |
|
|
|
|
|
| |
cellused (only non-space cells) because there may be cells with a
nondefault background.
|
| |
|
|
|
|
|
| |
options - choose the largest pane, which is more likely to be the one the
user wants to resize. Prompted by a report from Thomas Sattler.
|
| |
|
|
|
|
|
| |
specified a size with refresh-client -C. Prompted by a different change
with the same purpose from George Nachman.
|
|
|
|
|
| |
(that don't touch an edge). Move all the tty clear code into two common
functions rather than having the same bunch of checks everywhere.
|
|
|
|
| |
well.
|
| |
|
|
|
|
|
|
| |
copy mode), then look the key up in the table and fire any command
instead of delivering the key to the pane directly where it will be
ignored. This makes C-b C-b (send-prefix) work in copy mode again.
|
|
|
|
|
|
| |
itself hit the "terminal can't keep up" check. To avoid this, record how
much data we send during redraw (we know we will be starting with 0) and
skip the check until it has been flushed. GitHub issue 912.
|
| |
|
|
|
|
| |
conditional for key bindings.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
ROCHFORD.
|
|
|
|
|
|
|
|
|
|
|
| |
session:
pane-mode-changed
window-pane-changed
client-session-changed
session-window-changed
From Joshua Brot.
|
|
|
|
| |
so it can work when in -I, suggested by Suraj N Kurapati.
|