| Commit message (Collapse) | Author | Age |
... | |
|\| |
|
| | |
|
| | |
|
|\| |
|
| |
| |
| |
| | |
different without it.
|
| | |
|
| | |
|
| | |
|
|\| |
|
| |
| |
| |
| | |
history, from Olof-Joachim Frahm.
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
client.c
tmux.1
tmux.c
|
| |
| |
| |
| | |
every loop.
|
| |
| |
| |
| |
| |
| |
| | |
use event_once to queue a callback to deal with them. Also dead clients
with references would never actually be freed because the wrap-up
functions (the callback for stdin, or status_prompt_clear) would never
be called. So call them in server_client_lost.
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
server at a time; it may be toggled or cleared with select-pane -m and
-M (the border is highlighted). A new target '~' or '{marked}' specifies
the marked pane to commands and it is the default target for the
swap-pane and join-pane -s flag (this makes them much simpler to use -
mark the source pane and then change to the target pane to run swapp or
joinp).
|
|\| |
|
| |
| |
| |
| | |
cause libevent to go strange.
|
|\| |
|
| | |
|
|\| |
|
| |
| |
| |
| | |
generally (for example, again working in set-titles-string).
|
|\| |
|
| | |
|
| |
| |
| |
| | |
were only looking at the first winlink for a window in a session.
|
| | |
|
|\| |
|
| |
| |
| |
| | |
missing. Reported by Robin Powell.
|
|\|
| |
| |
| |
| | |
Conflicts:
format.c
|
| | |
|
| | |
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
Makefile
cmd-link-window.c
cmd-unlink-window.c
|
| | |
|
|\| |
|
| |
| |
| |
| | |
exits.
|
|\|
| |
| |
| |
| | |
Conflicts:
client.c
|
| |
| |
| |
| |
| | |
to using flock which actually works sensibly. Also always retry the lock
to fix a potential race, and add some extra logging.
|
|\| |
|
| |
| |
| |
| | |
deletion via the dead_key_bindings tree. From Keith Amling.
|
|\| |
|
| |
| |
| |
| | |
to be global. Move to paste.c.
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
Makefile
tmux.1
window.c
|
| | |
|
|\| |
|
| |
| |
| |
| |
| |
| | |
server until after the configuration file completes. This prevents it
racing against run-shell or if-shell in .tmux.conf that run in the
background.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
commands and allow a command to block execution of subsequent
commands. This allows run-shell and if-shell to be synchronous which has
been much requested.
Each client has a default command queue and commands are consumed one at
a time from it. A command may suspend execution from the queue by
returning CMD_RETURN_WAIT and then resume it by calling cmd_continue() -
for example run-shell does this from the callback that is fired after
the job is freed.
When the command queue becomes empty, command clients are automatically
exited (unless attaching). A callback is also fired - this is used for
nested commands in, for example, if-shell which can block execution of
the client's cmdq until a new cmdq becomes empty.
Also merge all the old error/info/print functions together and lose the
old curclient/cmdclient distinction - a cmdq is bound to one client (or
none if in the configuration file), this is a command client if
c->session is NULL otherwise an attached client.
|
| | |
|
| |
| |
| |
| | |
based on changes from Dagobert Michelsen.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
commands and allow a command to block execution of subsequent commands. This
allows run-shell and if-shell to be synchronous which has been much requested.
Each client has a default command queue and commands are consumed one at a time
from it. A command may suspend execution from the queue by returning
CMD_RETURN_WAIT and then resume it by calling cmd_continue() - for example
run-shell does this from the callback that is fired after the job is freed.
When the command queue becomes empty, command clients are automatically exited
(unless attaching). A callback is also fired - this is used for nested commands
in, for example, if-shell which can block execution of the client's cmdq until
a new cmdq becomes empty.
Also merge all the old error/info/print functions together and lose the old
curclient/cmdclient distinction - a cmdq is bound to one client (or none if in
the configuration file), this is a command client if c->session is NULL
otherwise an attached client.
|
| | |
|