dotfiles-nvim-lua. VS wezterm

I started using wezterm recently and really like it. It's cross platform and supports sixel graphics.

https://github.com/wez/wezterm

While WezTerm is a great terminal with sane defaults, it doesn't provide the default key binding to open the configuration file and edit it. That is understandable, everyone may have their own preference for that. Here we will figure out the recipe that would work everywhere and abide by modern standards.

Yeah, it's only for nvim or for your own lua projects.

For WezTerm annotations, afaik there is currently only an open issue without much progress: https://github.com/wez/wezterm/issues/3132

> [...] waiting for one or more terminal emulators to get together and add some ridiculous new escape codes [...]

I'm definitely of the opinion[0] that we haven't yet reached the limits of the "terminal emulator" UX paradigm.

The past few years do seem to have seen a resurgence in terminal emulator innovation due in part to a combination of new languages, the prevalence of GPUs, and a realisation that many of the existing terminal emulators weren't interested in any innovation in certain directions.

I've particularly been interested in the possibilities provided by the Terminal Graphics Protocol (which I discuss more in the linked comment).

A couple of years ago I switched to WezTerm[2] due to a combination of its graphics support, implementation language (Rust) and that its main developer seems to be interested in a combination of both solid support for existing standards & opportunities for innovation.

WezTerm also provides opportunities for customisation both in terms of shell integrations and of the application itself[3].

> [...] new escape codes [...]

Also, on this aspect, it may not even be necessary to create new escape codes--recently I discovered the `terminfo(5)` man page actually makes a pretty interesting read[7], in part because it lists some existing escape codes that seem like they have potential for re-use/re-implementation in the current day's more graphic-based systems.

---- footnotes ----

[0] As I mentioned in a recent comment on a thread[1] here:

"Motivated by the thought that at the current point in time perhaps the 'essence' of a 'terminal' is its linear 'chronological' presentation of input/interaction/output history rather than its use of 'text'."

[1] https://news.ycombinator.com/item?id=40475538

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

[3] While I'm definitely not a fan of the choice of Lua as the extension language, I have now at least hit my head against the wall[4] with it enough that I can actually get more complex custom functionality working.

[4] I've started to write up some of my Lua-related[5] notes & more general WezTerm[6] notes so hopefully it'll eventually be an easier road for others. :)

[5] https://gitlab.com/RancidBacon/floss-various-contribs/-/blob...

[6] https://gitlab.com/RancidBacon/notes_public/-/blob/main/note...

[7] As one does. :) It was a fascinating/amusing time capsule in terms(!) of mentions of weird hardware terminal quirks that at one time ("before my time") needed to be worked around; interesting escape code discoveries; and, the mention of a term I had not thought of for decades but was at one time of importance: NLQ! :D

wezterm or screen to see what's going on

I very well might be in the minority of Linux users, but I don't particularly care about the answers to most of these questions. I just want it to work. Give me solid defaults[0]. I'm not saying you shouldn't be able to override those defaults. That's an important feature of Linux.

My first experience running a cool-looking TUI file manager yesterday (I actually ended up trying yazi first) was that I got a lot of blank squares in place of missing icons and emojis due to missing fonts. I had to spend 20 minutes figuring that out before I got a good experience.

Interestingly, I also tried wezterm[1] in the process. It actually ships with the required fonts as fallback, but the version from my distro's package manager didn't work, while the AppImage did. I'm guessing my distro removed them, maybe for some of the reasons you cited. I started installing the nerd-fonts group for my distro. 6.5GB... no thanks. After manually poking through them and some googling I finally installed a couple and it's working now.

My overall point is that it's possible for app developers to provide good defaults like wezterm does. It's also possible for distro's to break those defaults.

[0]: https://blog.codinghorror.com/the-power-of-defaults/

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

wezterm (Linux, Macos & Windows)

wezterm is pretty good, I've been using it for a long time without any issues. The feature set is honestly huge and I'm probably using 10% of the capabilities, but I like having a lot of options.

Had the same on hyprland with wezterm and there is already a bug report open for it: https://github.com/wez/wezterm/issues/4483