From 8810ba5bd19ccb5f9a5e0ff813014f197543a61e Mon Sep 17 00:00:00 2001 From: nick black Date: Tue, 12 Jan 2021 03:24:27 -0500 Subject: [PATCH] xterm+256color2 is preferred over xterm+256color --- TERMS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TERMS.md b/TERMS.md index aa5b3688e..93cc33713 100644 --- a/TERMS.md +++ b/TERMS.md @@ -20,7 +20,7 @@ implementation of block-drawing characters, or relies on the font. | Linux console | ✔ | ✔ | N/A | `TERM=linux` `COLORTERM=24bit` | 8 (512 glyph fonts) or 16 (256 glyph fonts) colors max, but RGB values are downsampled to a 256-index palette. See below. | | FBterm | | ? | ? | `TERM=fbterm` | 256 colors, no RGB color. | | kmscon | | ? | ? | `TERM=xterm-256color` | No RGB color AFAICT, nor any distinct terminfo entry. | -| XTerm | | ✔ |🗴|`TERM=xterm-256color` `COLORTERM=24bit` | See note about DirectColor. Must configure with `--enable-direct-color`. `TERM=xterm-direct` seems to have the undesirable effect of mapping low RGB values to a palette; I don't yet understand this well. The problem is not seen with the specified configuration. Sixel support when built with `--enable-sixel-graphics` and run in vt340 mode. | +| XTerm | | ✔ |🗴|`TERM=xterm+256color2` `COLORTERM=24bit` | See note about DirectColor. Must configure with `--enable-direct-color`. `TERM=xterm-direct` seems to have the undesirable effect of mapping low RGB values to a palette; I don't yet understand this well. The problem is not seen with the specified configuration. Sixel support when built with `--enable-sixel-graphics` and run in vt340 mode. | | XFCE4 Terminal | ✔ | ✔ |? |`TERM=xfce` `COLORTERM=24bit` | No `xfce-direct` variant exists. | | Gnome Terminal | 🗴 | ✔ |? |`TERM=gnome` `COLORTERM=24bit` | `ccc` support *is* available when run with `vte-256color`. | | Konsole | 🗴 | ✔ |? | `TERM=konsole-direct` | |