aboutsummaryrefslogtreecommitdiff
path: root/tmux.h
diff options
context:
space:
mode:
authorNicholas Marriott <nicholas.marriott@gmail.com>2020-04-24 15:52:44 +0100
committerNicholas Marriott <nicholas.marriott@gmail.com>2020-04-24 15:52:44 +0100
commit527f66ed23a88a59fb3d8c1972336f55612059bf (patch)
treef5b23f00bd547d2d89777b93b49232498dcdf506 /tmux.h
parente67d65064e5541482990402fef85342f8cb4996b (diff)
downloadrtmux-527f66ed23a88a59fb3d8c1972336f55612059bf.tar.gz
rtmux-527f66ed23a88a59fb3d8c1972336f55612059bf.tar.bz2
rtmux-527f66ed23a88a59fb3d8c1972336f55612059bf.zip
Instead of having a default set of terminals in terminal-overrides that get XT
added and using that as a marker for xterm(1)-like, assume that if the terminfo(5) entry already has XT or the clear capability starts with CSI then the terminal is VT100-like and it should be safe to send DA requests. The DA responses trigger additional features being added. This is all to detect extensions if terminfo(5) is wrong or inadequate. If it fails, tmux will just fall back to using the capabilities in the terminfo(5) entry alone.
Diffstat (limited to 'tmux.h')
-rw-r--r--tmux.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/tmux.h b/tmux.h
index 2eb17ae0..fcf39bfb 100644
--- a/tmux.h
+++ b/tmux.h
@@ -1202,6 +1202,7 @@ struct tty_term {
#define TERM_DECSLRM 0x4
#define TERM_DECFRA 0x8
#define TERM_RGBCOLOURS 0x10
+#define TERM_VT100LIKE 0x20
int flags;
LIST_ENTRY(tty_term) entry;