| Commit message (Collapse) | Author | Age |
... | |
| | |
|
| | |
|
| |
| |
| |
| |
| | |
and in fact it is less useful that using the client ttyname. So don't bother
and don't pass it from the client. If we need it in future it is in c->environ.
|
| | |
|
| | |
|
| | |
|
|\|
| |
| |
| |
| | |
Conflicts:
tmux.h
|
| | |
|
| | |
|
| |
| |
| |
| | |
to use it, extended from a diff from George Nachman.
|
| |
| |
| |
| | |
is woken up again (with wait-for -S). From Thiago Padilha.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| | |
cmd_find_client to tell it whether or not to show errors, sometimes it's
needed and sometimes not.
|
| | |
|
| |
| |
| |
| | |
all on the stack.
|
| | |
|
| | |
|
| |
| |
| |
| | |
it, extended from a diff from George Nachman.
|
| |
| |
| |
| | |
wokrn up again (with wait-for -S). From Thiago Padilha.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| | |
tell it whether or not to show errors, sometimes it's needed and sometimes not.
|
| | |
|
| |
| |
| |
| | |
the stack.
|
| | |
|
| | |
|
| | |
|
|\|
| |
| |
| |
| |
| | |
Conflicts:
Makefile
grid-utf8.c
|
| | |
|
|\|
| |
| |
| | |
Sync from OpenBSD.
|
| |
| |
| |
| | |
numbered windows, from Raghavendra D Prabhu.
|
|\|
| |
| |
| | |
Sync from OpenBSD.
|
| |
| |
| |
| | |
works, reported by Drew Frank.
|
| |
| |
| |
| | |
working directory (like current process). From Marcel Partap.
|
| |
| |
| |
| | |
Thomas Adam.
|
| |
| |
| |
| |
| |
| | |
add a new value to mean "leave client running but don't attach" to fix
problems with using some commands in a command sequence. Most of the
work by Thomas Adam, problem reported by "jspenguin" on SF bug 3535531.
|
| | |
|
| |
| |
| |
| |
| | |
list. Change choose-window and -session to use the same code. From
Thomas Adam.
|
| |
| |
| |
| | |
reported by Giorgio Lando. Fix from Thomas Adam.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
-b flag to join-pane and move-pane to place the pane to the left or
above. From George Nachman.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
for home directory, . for server start directory, - for session start
directory and empty for the pane's working directory (the default). All
can also be used as part of a relative path (eg -/foo). Also provide -c
flags to neww and splitw to override default-path setting.
Based on a diff from sthen. ok sthen
|
| |
| |
| |
| | |
work from George Nachman.
|
| | |
|
| |
| |
| |
| |
| | |
on different machines regardless of where the user's home directory is.
ok nicm
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
default-path isn't empty, it is used. Otherwise:
1) If tmux neww is run from the command line, the working directory of the
client is used.
2) Otherwise sysctl KERN_PROC_CWD is used to retrieve the current
working directory of the process in the active pane.
3) If that fails, the directory where the session was created is used.
Support code by Romain Francois, OpenBSD specific bits by me.
Note this requires a recent userland and kernel with KERN_PROC_CWD.
|
| | |
|
| |
| |
| |
| | |
hierarchy and instead just look at what panes are actually in the window.
|