TERMS: remove bce column since we don't use bce

pull/1297/head
nick black 3 years ago
parent 97ccd0eee9
commit a0c700da86
No known key found for this signature in database
GPG Key ID: 5F43400C21CBFACC

@ -11,38 +11,37 @@ this variable, and your terminal doesn't actually support these sequences,
you're going to have a bad time.
The following have been established on a Debian Unstable workstation.
`ccc` is the Terminfo can-change-colors capability. `bce` is background
color erase. "Blocks" refers to whether the terminal provides its own
implementation of block-drawing characters, or relies on the font. Patches
to correct/complete this table are very welcome!
| Terminal | `ccc` | `bce` | Blocks | Recommended environment | Notes |
| --------------- | ----- | ----- | ------ | ------------------------------- | ----- |
| Alacritty | ✔ | ✔ |🗴 |`TERM=alacritty` `COLORTERM=24bit` | |
| FBterm | ? | ? |? |`TERM=fbterm` | 256 colors, no RGB color. |
| Gnome Terminal | 🗴 | ✔ |? |`TERM=gnome` `COLORTERM=24bit` | `ccc` support *is* available when run with `vte-256color`. |
| Guake | | | | | |
| ITerm2 | ? | ? |? | | |
| Kitty | ✔ | 🗴 |✔ |`TERM=xterm-kitty` | |
| kmscon | ? | ? |? |`TERM=xterm-256color` | No RGB color AFAICT, nor any distinct terminfo entry. |
| Konsole | 🗴 | ✔ |? |`TERM=konsole-direct` | |
| 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. |
| mlterm | 🗴 | ✔ |? |`TERM=mlterm-256color` | Do not set `COLORTERM`. `mlterm-direct` gives strange results. |
| PuTTY | ? | ? |? | | |
| rxvt | ? | ? |? | | |
| Sakura | ✔ | ✔ |? |`TERM=vte-256color` `COLORTERM=24bit` | No terminfo entry? |
| GNU Screen | 🗴 | ✔ |? |`TERM=screen.OLDTERM` | Must be compiled with `--enable-256color`. `TERM` should typically be `screen.` suffixed by the appropriate `TERM` value for the true connected terminal, e.g. `screen.vte-256color`. See below. |
| st | ✔ | ✔ |? |`TERM=st-256color` `COLORTERM=24bit` | |
| Terminator | ? | ? |? | ? | |
| Terminology | ? | ? |? | ? | |
| Tilda | ? | ? |? | ? | |
| tmux | ? | ? |? | ? | |
| wezterm | ✔ | ✔ |? |`TERM=wezterm` `COLORTERM=24bit` | |
| Windows Terminal| ? | ? |? | ? | |
| wterm | ? | ? |? | ? | |
| XFCE4 Terminal | ✔ | ✔ |? |`TERM=xfce` `COLORTERM=24bit` | No `xfce-direct` variant exists. |
| 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. |
| Yakuake | ? | ? |? | ? | |
`ccc` is the Terminfo can-change-colors capability. "Blocks" refers to whether
the terminal provides its own implementation of block-drawing characters, or
relies on the font. Patches to correct/complete this table are very welcome!
| Terminal | `ccc` | Blocks | Recommended environment | Notes |
| --------------- | ----- | ------ | ------------------------------- | ----- |
| Alacritty | ✔ |🗴 |`TERM=alacritty` `COLORTERM=24bit` | |
| FBterm | ? |? |`TERM=fbterm` | 256 colors, no RGB color. |
| Gnome Terminal | 🗴 |? |`TERM=gnome` `COLORTERM=24bit` | `ccc` support *is* available when run with `vte-256color`. |
| Guake | ? |? | | |
| ITerm2 | ? |? | | |
| Kitty | ✔ |✔ |`TERM=xterm-kitty` | |
| kmscon | ? |? |`TERM=xterm-256color` | No RGB color AFAICT, nor any distinct terminfo entry. |
| Konsole | 🗴 |? |`TERM=konsole-direct` | |
| 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. |
| mlterm | 🗴 |? |`TERM=mlterm-256color` | Do not set `COLORTERM`. `mlterm-direct` gives strange results. |
| PuTTY | ? |? | | |
| rxvt | ? |? | | |
| Sakura | ✔ |? |`TERM=vte-256color` `COLORTERM=24bit` | No terminfo entry? |
| GNU Screen | 🗴 |? |`TERM=screen.OLDTERM` | Must be compiled with `--enable-256color`. `TERM` should typically be `screen.` suffixed by the appropriate `TERM` value for the true connected terminal, e.g. `screen.vte-256color`. See below. |
| st | ✔ |? |`TERM=st-256color` `COLORTERM=24bit` | |
| Terminator | ? |? | ? | |
| Terminology | ? |? | ? | |
| Tilda | ? |? | ? | |
| tmux | ? |? | ? | |
| wezterm | ✔ |? |`TERM=wezterm` `COLORTERM=24bit` | |
| Windows Terminal| ? |? | ? | |
| wterm | ? |? | ? | |
| XFCE4 Terminal | ✔ |? |`TERM=xfce` `COLORTERM=24bit` | No `xfce-direct` variant exists. |
| 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. |
| Yakuake | ? |? | ? | |
Note that `xfce4-terminal`, `gnome-terminal`, etc. are essentially skinning
atop the common VTE ("Virtual TErminal") library.
@ -60,8 +59,8 @@ https://github.com/kovidgoyal/kitty/issues/3185 and
https://github.com/dankamongmen/notcurses/issues/1117. This behavior can
be demonstrated with the `kittyzapper` binary (`src/poc/kittyzapper.c`).
Kitty is furthermore the only terminal I know to lack the `bce` capability, but
Notcurses never relies on `bce` behavior.
Kitty is furthermore the only terminal I know to lack the `bce` (Background
Color Erase) capability, but Notcurses never relies on `bce` behavior.
## GNU screen

Loading…
Cancel
Save