chips-test VS iterm2

I tinkered a bit with sixel support for my "C64 emulator in the terminal" (https://github.com/floooh/docker-c64), but unfortunately it's way too slow to get anywhere near 'realtime' output (30fps or better).

Here's the (abandondend) sixel-version source code, only with two colors, more color planes would drastically reduce the performance.

https://github.com/floooh/chips-test/blob/master/examples/as...

I really wish there was a decent pixel-framebuffer standard for terminals (with at least the same performance as curses). This would allow a lot of fun "terminal applications" (e.g. everything that used to run in VGA Mode 13h).

What terminal emulator are you using? I have noticed that the latest release of iterm2 has problems rendering glyphs (see this discussion and links therein). I too am having problems displaying any nerd font icon due to the aforementioned.

Found the bug report related: https://gitlab.com/gnachman/iterm2/-/issues/9372

2 things to note:

- This bug has 12 +1s, which suggests it was never very widespread (I could be wrong); and

- Big Sur was 2 major releases ago.

Like I mentioned, I never saw this issue, and had never heard of it despite the fact that probably about half the people I work with use Macs, and I believe nearly all of them use iTerm2.

I had trouble getting the tmux setup working in iterm.

The main page suggests -CC, but the best practices wiki[0] says to use `-CC new -A -s main`, but this causes iterm to warn that a session is already started and doesn't actually create or reattach like I expected. I also had trouble getting the tmux select-layout to work: when I tried it all my panes just exited with an error. I would like to have iterm behave similarly to Kitty's tall layout[1] which I think is the same thing as tmux's main layout, but haven't figured out how to make it work. Anybody have tips on making these wek?

[0]: https://gitlab.com/gnachman/iterm2/-/wikis/tmux-Integration-...

The latest version (v3.4.16) was released 3 months ago.

https://gitlab.com/gnachman/iterm2/-/tags/v3.4.16

See https://gitlab.com/gnachman/iterm2/-/issues/6167

I just found this, the synchronized updates spec from iTerm2: https://gitlab.com/gnachman/iterm2/-/wikis/synchronized-upda...

Googling for it, it seems some other terminals implement this as well.

According to https://gitlab.com/gnachman/iterm2/-/issues/8827, this occurs when "reporting is enabled". This means that mouse clicks are reported as special events to the application running in the terminal rather than being handled by the terminal emulator itself. According to https://iterm2.com/documentation-preferences-profiles-terminal.html, you can temporarily disable it by holding down Option.

I take it that the main at the end of the command in this screenshot is the name of the session?