| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |\| |
|
| | | |
|
| |\| |
|
| | |
| |
| |
| |
| | |
if you exit and reenter copy mode (it doesn't remember the position,
just the search string), suggested by espie@.
|
| |\|
| |
| |
| |
| | |
Conflicts:
format.c
|
| | |
| |
| |
| | |
conditional for key bindings.
|
| | |
| |
| |
| | |
ROCHFORD.
|
| |\| |
|
| | |
| |
| |
| | |
so it can work when in -I, suggested by Suraj N Kurapati.
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
and not have to wait for an update when they change pane, we allow
commands to run more than once a second if the expanded form
changes. Unfortunately this can mean them being run far too often
(pretty much continually) when multiple clients exist, because some
formats (including #D) will always differ between clients.
To avoid this, give each client its own tree of jobs which means that
the same command will be different instances for each client - similar
to how we have the tag to separate commands for different panes.
GitHub issue 889; test case reported by Paul Johnson.
|
| |\| |
|
| | |
| |
| |
| | |
structure.
|
| |\| |
|
| | | |
|
| | |
| |
| |
| | |
return a buffer from the stack.
|
| | |
| |
| |
| |
| |
| |
| | |
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.
|
| |\| |
|
| | |
| |
| |
| | |
pattern.
|
| |\|
| |
| |
| |
| | |
Conflicts:
server.c
|
| | |
| |
| |
| |
| | |
to -t instead of a target session. Also allow them to contain only one
session.
|
| |\| |
|
| | | |
|
| |\| |
|
| | |
| |
| |
| |
| |
| | |
jobs, this means that if the same job is used for different windows or
panes (for example in pane-border-format), it will be run separately for
each pane.
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |\| |
|
| | |
| |
| |
| | |
not string.
|
| |\| |
|
| | | |
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
commands this pushes more of the code into options.c and ties it more
closely to the options table rather than having an unnecessary
split. Also add support for array options (will be used later). Only
(intentional) user visible change is that show-options output is now
passed through vis(3) with VIS_DQ so quotes are escaped.
|
| |\| |
|
| | | |
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| | |
are expanded so can compare formats). And expand the condition to
#{?a,b,c} (the "a" part) if it doesn't work as a simple lookup.
Also add FORMAT_NOJOBS flag to disable jobs in a format.
|
| | | |
|
| |\| |
|
| | |
| |
| |
| |
| | |
again if the expanded form changes (otherwise at most once per second as
usual). Fixes issues reported by Gregory Pakosz.
|
| |\| |
|
| | |
| |
| |
| |
| | |
that the user can get at additional information - now used for the
"hook" format, more to come.
|
| | | |
|
| |\| |
|
