| Age | Commit message (Collapse) | Author |
|---|
|
environment. Previously it came from the session environment. From J
Raynor.
|
|
|
|
doesn't make much sense as a session option.
|
|
|
|
|
|
descriptors rather than strings.
- Each session still has a current working directory.
- New sessions still get their working directory from the client that
created them or its attached session if any.
- New windows are created by default in the session working directory.
- The -c flag to new, neww, splitw allows the working directory to be
overridden.
- The -c flag to attach let's the session working directory be changed.
- The default-path option has been removed.
To get the equivalent to default-path '.', do:
bind c neww -c $PWD
To get the equivalent of default-path '~', do:
bind c neww -c ~
This also changes the client identify protocol to be a set of messages rather
than one as well as some other changes that should make it easier to make
backwards-compatible protocol changes in future.
|
|
|
|
|
|
|
|
|
|
session exists. If -A is used, -D behaves like -d to attach-session.
|
|
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.
|
|
|
|
from 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.
|
|
|
|
|
|
|
|
stubs but will be filled in for control mode later. From George Nachman.
|
|
George Nachman.
|
|
|
|
even if given with, for example, -t '', and explicitly forbid empty
session names and those containing a : when they are created.
|
|
unattached sessions when choosing the most recently used (if -t is not
given). Suggested by claudio@.
|
|
|
|
window if created detached with -d.
|
|
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.
|
|
this screws up the choice of most-recently-used. Instead, break the time
update into a little function and do it when the session is attached.
Pointed out by joshe@.
|
|
|
|
a key binding (L) to move a client back to its last session.
|
|
option to default to empty and make that mean that the stored session CWD is
used.
|
|
Micah Cowan.
|
|
|
|
|
|
collecting all the errors, then start with the active window in more mode
displaying them.
|
|
time now I've configured emacs to make them displayed in really annoying
colours...
|
|
the rest to reduce lint output.
|
|
command entry structs and a couple of functions to check/set the flags.
|
|
attached, rather than every event loop.
|
|
so on but where the linked windows are synchronized (ie creating, killing
windows and so on are mirrored between the sessions). A grouped session may be
created by passing -t to new-session.
Had this around for a while, tested by a couple of people.
|
|
|
|
forkpty do it and then alter the bits that should be changed after fork. A
little neater and more portable.
|
|
|
|
new windows.
|
|
|
|
comment.
|
|
|
|
for an index for a new window.
|
|
session detached, let the caller do it. Allows "tmux new -d \; attach" to work.
|
|
terminal, copy the termios(4) special characters and use them for new windows
created in the new session. Suggested by Theo.
|
|
within tmux.
There is a global environment, copied from the external environment when the
server is started and each sesssion has an (initially empty) session
environment which overrides it.
New commands set-environment and show-environment manipulate or display the
environments.
A new session option, update-environment, is a space-separated list of
variables which are updated from the external environment into the session
environment every time a new session is created - the default is DISPLAY.
|
