iterm2 VS termite

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?

- you can also rectangular select like in vim, and then press either p (includes LF) or which joins the multiline clipboard text into a single line (removing LF's), that payed off a lot for output like `git status` and wanting to operate on parts of the output (files e.g.)

Have a look at the still young website's documentation here: https://contour-terminal.org/input-modes/#supported-text-obj...

for a more complete look of what you can do with the keyboard (normal mode) :)

[1] https://github.com/thestinger/termite/

Also, regarding VTE, the author of termite (discontinued terminal emulator) expressed similar concerns about the GNOME devs. Apparently, they have little interest in making the library useful to people not working on GNOME apps: https://github.com/thestinger/termite

Termite is obsolete by Alacritty.

I simply do not want to use anything libvte based. And that's what sakura is and termite used to be.

History and experience tells a different story [1]. Never trust a library that is maintained by GNOME.

1.: https://github.com/thestinger/termite

This post by the Termite developer, with respect to VTE, is quite instructive

> https://github.com/thestinger/termite/blob/master/README.rst...

Wow, this confirms a lot of my impressions:

>> In 2012, we submitted a tiny patch exposing the APIs needed for the keyboard text selection, hints mode and other features. Despite support from multiple other projects, the patch was rejected. It's now almost a decade later and no progress has been made. There is no implementation of these kinds of features in VTE and it's unlikely they'll be provided either internally or as flexible APIs. This is the tip of the iceberg when it comes to their hostility towards other projects using VTE as a library. GTK and most of the GNOME project are much of the same. Avoid them and don't make the mistake of thinking their libraries are meant for others to use.

This is exactly why sixel-tmux exists as a separate entity!

> Yeah, I read the entire conversation and if sixel support lands in tmux upstream, it would indeed be good news.

I'll keep my fingers crossed, but right now, there seems to be a lot of good will. I will do everything I can.