| Commit message (Collapse) | Author | Age |
... | |
| |
|
|
|
|
|
|
| |
is being written and when.
Also a manpage typo fix from jmc@.
|
| |
|
|
|
|
| |
already an absolute position.
|
|
|
|
| |
possible instead of sending individual line feeds.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
together instead of handling them one by one. This is significantly
faster. Sequences are terminated when we reach the end of the line, fill
the internal buffer, or a different character is seen by the input
parser (an escape sequence, or UTF-8).
Rather than writing collected sequences out immediately, hold them until
it is necessary (another screen modification, or we consume all
available data). This means we can discard changes that would have no
effect (for example, lines that would just be scrolled off the screen or
cleared). This reduces the total amount of data we write out to the
terminal - not important for fast terminals, but a big help with slow
(like xterm).
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
is not actually helping us much and just adds complexity, so don't
bother.
|
|
|
|
| |
actually want.
|
|
|
|
|
| |
extra scroll of the entire terminal; issuing DECSTBM first prevents
this. Do that for now.
|
|
|
|
|
| |
not reset colours when in SGR 0), so we can't use it without more
trouble than it is worth. Abandon the idea for now.
|
|
|
|
| |
others for clearing panes.
|
|
|
|
| |
is the same as the previous one.
|
| |
|
|
|
|
| |
the whole line.
|
|
|
|
|
|
|
|
|
|
|
| |
main issue is that if we have two panes, A with 1002 and B with 1003, we
need to set 1003 outside tmux in order to get all the mouse events, but
then we need to suppress the ones that pane A doesn't want. This is easy
in SGR mouse mode, because buttons == 3 is only used for movement events
(for other events the trailing m/M marks a release instead), but in
normal mouse mode we can't tell so easily. So for that, look at the
previous event instead - if it is drag+release as well, then the current
event is a movement event.
|
|
|
|
| |
the terminal has >=16 colours.
|
| |
|
| |
|
|
|
|
| |
check in server_client_handle_key, and tweak a comment.
|
| |
|
|
|
|
| |
from S Gilles.
|
|
|
|
| |
the same line_, fixes redraw bug reported by patrick keshishian.
|
| |
|
|
|
|
|
| |
yoff (because they are both already relative to the pane). Also fix some
other minor nits.
|
|
|
|
| |
full width and at the edge of the region), otherwise clear the region entirely.
|
|
|
|
| |
feeds, and do not move cursor to end for full width panes).
|
| |
|
|
|
|
|
|
|
| |
supports them (that is, if it advertises itself as a VT420 - probably
just xterm). These are the vertical equivalent of the scroll region and
allow much faster scrolling of panes that do not take up the full width
of the terminal.
|
|
|
|
|
| |
using a wrong TERM without xenl is not so broken if used on a sensible
terminal.
|
|
|
|
|
|
|
|
|
|
|
|
| |
sequences (notable EL and ED but also IL, DL, ICH, DCH) create blank
cells using the current background colour rather than the default
colour.
On modern systems BCE doesn't really have many benefits, but most other
terminals now support it, some (lazy) applications rely on it, and it is
not hard to include now that we have pane background colours anyway.
Mostly written by Sean Haugh.
|
|
|
|
| |
pane. Reported by Theo Buehler.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
instead track them as change (dirty) and update them once at the end,
saves much time if repeatedly writing the same cell. Also fix comparison
of cells being equal in a few places (memcmp is not enough).
|
|
|
|
| |
unless they have changed.
|
|
|
|
|
| |
is normally better because using cub1 will be ^H^H (so two bytes) but
cub would be ^[[2D (four).
|
| |
|
|
|
|
| |
that happens when working out if they are supported.
|
|
|
|
|
|
|
|
| |
wasting unnecessary space. The 'Tc' flag must be set in the external
TERM entry (using terminal-overrides or a custom terminfo entry), if not
tmux will map to the closest of the 256 or 16 colour palettes.
Mostly from Suraj N Kurapati, based on a diff originally by someone else.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
poor idea that was fairly quickly replaced by SGR mouse input (which is
now widespread). It is impossible to tell the difference between UTF-8
and non-UTF-8 mouse input; since the mouse-utf8 option was removed tmux
has not handled it correctly in any case; and it is ridiculous to have
three different forms of mouse input.
|
| |
|