| Commit message (Collapse) | Author | Age |
... | |
| |
| |
| |
| | |
for client and tree, and by name and content for buffer.
|
|\|
| |
| |
| |
| |
| | |
Conflicts:
tmux.1
window.c
|
| |
| |
| |
| |
| | |
we currently only have two log levels so just use -v and -vv rather than
-v and -vvvv, and clarify the man page entry for -v.
|
| | |
|
|\| |
|
| |
| |
| |
| | |
sequencess.
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
Makefile.am
cfg.c
server-client.c
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|\| |
|
| | |
|
|\| |
|
| | |
|
|\| |
|
| | |
|
|\| |
|
| |
| |
| |
| | |
well.
|
|\|
| |
| |
| |
| | |
Conflicts:
format.c
|
| |
| |
| |
| | |
conditional for key bindings.
|
| |
| |
| |
| | |
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.
|
|\| |
|
| | |
|
|\| |
|
| | |
|
|\| |
|
| |
| |
| |
| |
| |
| |
| | |
must be a full line). Don't let it redraw the status line more than once
a second.
Requested by someone about 10 years ago...
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
reasonable amount (currently width * height * 8 bytes), discard all
output to the terminal and start trying to redraw periodically
instead. Continue with this until the amount of data we are trying to
write falls to a low level again.
This helps to prevent tmux sitting on a huge buffer of data when there
are processes with fast output running inside tmux but the outside
terminal is slow.
A new client_discarded format holds the amount of data that has been
discarded due to this mechanism.
The three variables (when to start this, when to stop, and how often to
redraw) are basically "works for me" at the moment, this is going in to
see how it goes and if it causes problems for anyone else.
|
|\| |
|
| | |
|
|\|
| |
| |
| |
| |
| | |
Conflicts:
server-client.c
tmux.1
|
| |
| |
| |
| |
| |
| |
| | |
falls back to an alternative if the tty name is not available. This is
clearer than overloading the client ttyname member and allows us to
remove the path stored in the tty struct, it should always be the same
as the client.
|
|\| |
|
| |
| |
| |
| |
| | |
terminfo capability. This means there are now nine attribute bits, so
anything above 0xff uses an extended cell.
|
|\| |
|
| | |
|
|\|
| |
| |
| |
| | |
Conflicts:
server.c
|
| |
| |
| |
| |
| |
| | |
is being written and when.
Also a manpage typo fix from jmc@.
|
| |
| |
| |
| |
| | |
to -t instead of a target session. Also allow them to contain only one
session.
|
| | |
|
|\| |
|
| | |
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|\| |
|
| | |
|
|\| |
|