iTerm2-Color-Schemes VS wezterm

Script for changing/testing terminal colors: https://github.com/mbadolato/iTerm2-Color-Schemes

FWIW, if you submit your iterm2 colors to https://github.com/mbadolato/iTerm2-Color-Schemes you get many terminals "for free".

Install iterm2 themes

I’ve been a fan of Mark Badolato’s collection of themes. Do check them out here, if you haven’t already: https://github.com/mbadolato/iTerm2-Color-Schemes

cd Downloads wget https://github.com/mbadolato/iTerm2-Color-Schemes/archive/refs/heads/master.zip unzip master.zip

Change the colour scheme: I made my own colour scheme. If you are searching, this repo is a great source for colour schemes for many different terminal apps.

- [Wezterm](https://github.com/wez/wezterm)

and my own humble entry in this space is wezterm: https://wezfurlong.org/wezterm which has a decent population of users in Japan and a handful of arabic/RTL users for the unfinished bidi support.

Take a look at https://github.com/wez/wezterm/issues/784 which tracks BIDI/RTL support in wezterm (for eg: Arabic scripts) to get a sense of the difficulty.

either Wezterm OR Window-terminal i Personally use WindowTERM with alacritty * when needed since WindowTerm has some weird ncurses issues ,

AFAIK wezterm[1] and warp[2] are built on top of the WebGPU

[1] https://wezfurlong.org/wezterm/

[2] https://www.warp.dev

In XTerm, this (rightly) makes no difference. In Foot and Contour however, you still end up a line resp. a screen below where you started, if now with the correct horizontal position.

So it seems to me like what you want should work by default, except it doesn’t.

It should be possible to instead just treat the whole thing as a graphical overlay (by computing or directly asking for the character cell size, as Kirill Panov rightly admonishes me is possible with XTWINOPS) without touching the cursor; that’s what the “sixel scrolling” setting (DECSDM) is supposed to do. Then you can just manually move the cursor forward however many positions after you’re done drawing.

Except apparently the DEC manual (the VT330/340 one above) and DEC hardware contradict each other as to which setting of DECSDM (set or reset) corresponds to which scrolling state (enabled or disabled), and XTerm has implemented it according to the manual not the VT3xx[1,2,3]—then most other emulators followed suit[4]—then XTerm switched to following the hardware[5,6] (unless you and that’s what I’m seeing on my machine right now. So now you need to check if you’re on XTerm ≥ 369 or not[7]. If I’m reading the Notcurses code right, other terminals have followed suit[8].

Again, ouch.

P.S. It seems DEC had an internal doc for how their terminals should operate (DEC STD 070) [9]. It does not document DECSDM at all.

[1] https://github.com/wez/wezterm/issues/217#issuecomment-86449...

[2] https://github.com/hackerb9/lsix/issues/41

[3] https://github.com/dankamongmen/notcurses/issues/1782

[4] https://github.com/arakiken/mlterm/pull/23

[5] https://invisible-island.net/xterm/xterm.log.html#xterm_369

[6] https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h3-T...

[7] https://github.com/dankamongmen/notcurses/commit/0918fa251e2... (the correct version cutoff is 369 not 359, the patch contains a now-fixed bug)

[8] https://github.com/dankamongmen/notcurses/blob/master/src/li... (look for mentions of invertsixel)

[9] http://www.bitsavers.org/pdf/dec/standards/EL-SM070-00_DEC_S...

I use Wezterm as my editor and the built-in functionality for pane splitting (which means I don't run tmux as I used to do).

Starting with wezterm 20221119-145034-49b9839f I've noticed a problem when using Neovim's :terminal. The problem is this: