| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
| |
add a limit of how much data will be sent to the client and try to use
it for panes with some degree of fairness. GitHub issue 2217, with
George Nachman.
|
| |
|
|
| |
use more clearly defined and preparation for some future work).
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
not attached, the server process asks it to open the file, similar to
how works for stdin, stdout, stderr. This makes special files like
/dev/fd/X work (used by some shells). stdin, stdout and stderr and
control mode are now just special cases of the same mechanism. This will
also make it easier to use for other commands that read files such as
source-file.
|
| | |
|
| |
|
|
| |
Also man page fixed from jmc.
|
| |
|
|
|
|
| |
and the previous restored when the top is exited. If a mode that is
already on the stack is entered, the existing instance is moved to the
top as the active mode rather than being opened new.
|
| | |
|
| |
|
|
|
|
| |
CMD_FIND_* flags in the cmd_entry and call it for the command. Commands
with special requirements call it themselves and update the target for
hooks to use.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
handling.
|
| | |
|
| |
|
|
| |
using an enum and simplify the parsing code.
|
| |
|
|
| |
about the order.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the state (client, session, winlink, pane) for it it before entering the
command. Each command provides some flags that tell the prepare step
what it is expecting.
This is a requirement for having hooks on commands (for example, if you
hook "select-window -t1:2", the hook command should to operate on window
1:2 not whatever it thinks is the current window), and should allow some
other target improvements.
The old cmd_find_* functions remain for the moment but that layer will
be dropped later.
Joint work with Thomas Adam.
|
| |
|
|
| |
continue if the send fails.
|
| |
|
|
| |
Buehler.
|
| | |
|
| |
|
|
| |
saved_cursor_[xy] formats as a side-effect).
|
| | |
|
| |
|
|
|
|
|
|
|
| |
directly with a helper function in the cmd_entry, include a table of
bind-key commands and pass them through the command parser and a
temporary cmd_q.
As well as being smaller, this will allow default bindings to be command
sequences which will probably be needed soon.
|
| | |
|
| |
|
|
| |
to faff around with huge numbers to get everything.
|
| |
|
|
|
|
|
|
| |
much as before - buffers are automatically named "buffer0000",
"buffer0001" and so on and ordered as a stack. Buffers can be named
explicitly when creating ("loadb -b foo" etc) or renamed ("setb -b
buffer0000 -n foo"). If buffers are named explicitly, they are not
deleted when buffer-limit is reached. Diff from J Raynor.
|
| |
|
|
| |
to be global. Move to paste.c.
|
| | |
|
| |
|
|
| |
Nachman.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
wrapped line, based on a diff from George Nachman.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
SHRT_MIN. From Chris Johnsen.
|
| | |
|
| | |
|
| |
|
|
|
| |
negative to capture part of the history. Prompted by request from Victor
J Orlikowski.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Originally, tmux commands were parsed in the client process into a
struct with the command data which was then serialised and sent to the
server to be executed. The parsing was later moved into the server (an
argv was sent from the client), but the parse step and intermediate
struct was kept.
This change removes that struct and the separate parse step. Argument
parsing and printing is now common to all commands (in arguments.c) with
each command left with just an optional check function (to validate the
arguments at parse time), the exec function and a function to set up any
key bindings (renamed from the old init function).
This is overall more simple and consistent.
There should be no changes to any commands behaviour or syntax although
as this touches every command please watch for any unexpected changes.
|
| | |
|
| |
|
|
|
|
|
| |
much more convenient and also simplifies lot of code. This renders
copy-buffer useless and makes buffer-limit now a server option.
By Tiago Cunha.
|
| | |
|
| |
|
|
|
| |
time now I've configured emacs to make them displayed in really annoying
colours...
|
|
|
buffer. From Jonathan Alvarado.
|
