| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
| |
when the first client has identified) so all the client formats are
available, fixes problems reported by Thomas Sattler.
|
|
|
|
| |
Morten M Neergaard in GitHub issue 1782.
|
|
|
|
|
|
| |
to start, otherwise commands like lsk which start the server again can
end up looping infinitely. Also make the first client exit
correctly. Problem reported by Wael M Nasreddine.
|
|
|
|
| |
processing code.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
generic and hide the display-panes specific bits into
cmd-display-panes.c.
|
|
|
|
|
|
| |
immediately rather than queuing them (the command can block the queue
which means they were not being seen until it finished which was too
late). Reported by denis@ and solene@, ok solene@.
|
|
|
|
| |
split-window or display-message -I.
|
|
|
|
|
| |
into the mouse event that later code uses, it has been adjusted and they
should use the original position. GitHub issue 1710.
|
| |
|
|
|
|
|
| |
command queue so they are ordered correctly with the commands that they
execute.
|
| |
|
|
|
|
| |
parts of the status line, from Avi Halachmi.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
changes to allow the status line to be entirely configured with a single
option.
Now that it is possible to configure their content, enable the existing
code that lets the status line be multiple lines in height. The status
option can now take a value of 2, 3, 4 or 5 (as well as the previous on
or off) to configure more than one line. The new status-format array
option configures the format of each line, the default just references
the existing status-* options, although some of the more obscure status
options may be eliminated in time.
Additions to the #[] syntax are: "align" to specify alignment (left,
centre, right), "list" for the window list and "range" to configure
ranges of text for the mouse bindings.
The "align" keyword can also be used to specify alignment of entries in
tree mode and the pane status lines.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
| |
return NULL. GitHub issue 1547.
|
|
|
|
|
| |
an entirely new key press, not checked in root table and ignored if not
found. GitHub issue 1513.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
been a limitation for a long time.
There are two new options, window-size and default-size, and a new
command, resize-window. The force-width and force-height options and the
session_width and session_height formats have been removed.
The new window-size option tells tmux how to work out the size of
windows: largest means it picks the size of the largest session,
smallest the smallest session (similar to the old behaviour) and manual
means that it does not automatically resize windows. The default is
currently largest but this may change. aggressive-resize modifies the
choice of session for largest and smallest as it did before.
If a window is in a session attached to a client that is too small, only
part of the window is shown. tmux attempts to keep the cursor visible,
so the part of the window displayed is changed as the cursor moves (with
a small delay, to try and avoid excess redrawing when applications
redraw status lines or similar that are not currently visible). The
offset of the visible portion of the window is shown in status-right.
Drawing windows which are larger than the client is not as efficient as
those which fit, particularly when the cursor moves, so it is
recommended to avoid using this on slow machines or networks (set
window-size to smallest or manual).
The resize-window command can be used to resize a window manually. If it
is used, the window-size option is automatically set to manual for the
window (undo this with "setw -u window-size"). resize-window works in a
similar way to resize-pane (-U -D -L -R -x -y flags) but also has -a and
-A flags. -a sets the window to the size of the smallest client (what it
would be if window-size was smallest) and -A the largest.
For the same behaviour as force-width or force-height, use resize-window
-x or -y, and "setw -u window-size" to revert to automatic sizing..
If the global window-size option is set to manual, the default-size
option is used for new windows. If -x or -y is used with new-session,
that sets the default-size option for the new session.
The maximum size of a window is 10000x10000. But expect applications to
complain and much higher memory use if making a window excessively
big. The minimum size is the size required for the current layout
including borders.
The refresh-client command can be used to pan around a window, -U -D -L
-R moves up, down, left or right and -c returns to automatic cursor
tracking. The position is reset when the current window is changed.
|
|
|
|
| |
fix from Avi Halachmi.
|
|
|
|
|
| |
C-y, only use the top buffer if no text has previously been killed. This
and previous change promped by discussion with kn@.
|
|
|
|
| |
right parts of the status line.
|
|
|
|
| |
hasn't changed, needed for resizing.
|
|
|
|
| |
all just use the three flags together (window, borders, status).
|
|
|
|
| |
count instead.
|
| |
|
|
|
|
|
| |
not the any key. Also rename some labels. Fixes GitHub issue 1406
reeported by Mark Kelly.
|
|
|
|
| |
in the current key table. GitHub issue 1404.
|
| |
|
|
|
|
|
| |
the cwd, and do not fall back to "." as it is pretty useless. GitHub
issue 1331.
|
|
|
|
|
| |
not exit until jobs started from run-shell/if-shell have finished (add a
job flags member and a flag to indicate other jobs). GitHub issue 1245.
|
|
|
|
| |
set. GitHub issue 1239.
|
|
|
|
| |
used yet but will be soon. From Thomas Adam.
|
|
|
|
| |
1201.
|
|
|
|
| |
still only one is allowed but this lets tmux draw bigger ones.
|
|
|
|
| |
the pane has already died).
|
|
|
|
| |
Thomas Sattler.
|
|
|
|
| |
timeout. From Laurens Post.
|
|
|
|
|
|
|
| |
may be needed for all of them, so don't delete it on the first; and
don't skip setting the redraw flag if the timer is already running.
Reported by Pol Van Aubel in GitHub issue 1003.
|
| |
|