| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
Changes in the imsg API need to be reflected here as tmux wasn't creating
any clients because of it.
|
|
|
|
|
| |
Linux and friends don't natively have fparseln() so add it to compat/ and
ensure autotools can pick it up.
|
|\
| |
| |
| |
| | |
Conflicts:
client.c
|
| |
| |
| |
| | |
really worked properly and is rarely used.
|
| |
| |
| |
| | |
to do this along later for those who want it.
|
| |
| |
| |
| |
| | |
to using flock which actually works sensibly. Also always retry the lock
to fix a potential race, and add some extra logging.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
entry:
F13-F24 are S-F1 to S-F12
F25-F36 are C-F1 to C-F12
F37-F48 are C-S-F1 to C-S-F12
F49-F60 are M-F1 to M-F12
and F61-F63 are M-S-F1 to M-S-F3
This should be no difference for applications inside tmux, but means
that any key binding for F13 will need to be replaced by S-F1 and so on.
|
| |
| |
| |
| | |
the other functions.
|
| |
| |
| |
| | |
ok nicm@
|
| |
| |
| |
| |
| | |
MSG_EXITED dance, don't try to resume it since a) it's pointless and b)
the tty structures have been cleaned up and tmux will crash.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
PS_{ZOMBIE,EMBRYO} on the process instead of peeking into the process's
thread data. This eliminates the need for the thread-level SDEAD state.
Change kvm_getprocs() (both the sysctl() and kvm backends) to report the
"most active" scheduler state for the process's threads.
tweaks kettenis@
feedback and ok matthew@
|
| |
| |
| |
| |
| |
| | |
fparseln instead of reimplementing it on our own.
with input by and ok nicm@
|
| |
| |
| |
| | |
sf dot net.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
It's tedious having to tell people all the time to try the Git version to
see if a given problem is reproducible; put this in the FAQ and hope people
read it.
|
|\ \ |
|
| | | |
|
| |\| |
|
| | |
| | |
| | |
| | | |
to faff around with huge numbers to get everything.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
this causes confusion when tmux uses SGR outside but the application
inside tmux is using conventional xterm mouse reporting. So suppress
obviously bad input. From Timothy Allen, SF bug 128.
|
| | |
| | |
| | |
| | | |
drawing rather than just treating them as SO and SI.
|
| | |
| | |
| | |
| | | |
don't get stuck.
|
| | |
| | |
| | |
| | | |
Balazs Kezes.
|
| | | |
|
| | |
| | |
| | |
| | | |
Amling.
|
| | | |
|
| | |
| | |
| | |
| | | |
deletion via the dead_key_bindings tree. From Keith Amling.
|
| | | |
|
|/ / |
|
|\ \ |
|
| | | |
|
|/ / |
|
|\ \ |
|
| | |
| | |
| | |
| | | |
This is needed, otherwise tzset() is undefined.
|
| |\|
| | |
| | |
| | |
| | |
| | | |
Conflicts:
format.c
window.c
|
| | |
| | |
| | |
| | |
| | |
| | | |
split-window, respawn-window or respawn-pane, pass them directly to
execvp() to help avoid quoting problems. One argument still goes to "sh
-c" like before. Requested by many over the years. Patch from J Raynor.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
|
| | |
| | |
| | |
| | | |
normally does nothing), from Marcel Partap.
|
| | |
| | |
| | |
| | |
| | | |
instead. Means modifier keys still increase the line count, just not as
much. Based on a diff from Marcel Partap.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
irritating flaws:
a) The old way of always using the top or left if the choice is
ambiguous is annoying when the layout is unbalanced.
b) The new way of remembering the last used pane is annoying if the
layout is balanced and the leftmost is obvious to the user (because
clearly if we go right from the top-left in a tiled set of four we want
to end up in top-right, even if we were last using the bottom-right).
So instead, use a combination of both: if there is only one possible
pane alongside the current pane, move to it, otherwise choose the most
recently used of the choice.
|
| | | |
|
|/ / |
|
|\| |
|
| | |
|