Wez Furlong

wezterm currently only captures the zone type into the data model.

The critical part of the versioning is the CODEC_VERSION, which is bumped when ABI changes are made: https://github.com/wez/wezterm/blob/6b67ae842cdd156490b598fe6ce2ce983a70b2a8/codec/src/lib.rs#L416-L419 that is what is checked by the client when it comes to...

Yeah, all the windows are rounded on macOS, so I considered it a bug. I'll accept a PR for something around this. I'm not super sure what the config should...

An issue with just using `SQUARE_CORNER` is that it implies that not specifying it will give something other than square corners, but most systems only have square corners, and there...

color_scheme takes precedence over `colors`. See https://github.com/wez/wezterm/issues/2376

This is now implemented now in `main`: * [cursor_thickness](https://wezfurlong.org/wezterm/config/lua/config/cursor_thickness.html), [underline_thickness](https://wezfurlong.org/wezterm/config/lua/config/underline_thickness.html), [underline_position](https://wezfurlong.org/wezterm/config/lua/config/underline_position.html) and [strikethrough_position](https://wezfurlong.org/wezterm/config/lua/config/strikethrough_position.html) options to fine tune appearance. It typically takes about an hour before commits are available as nightly...

https://terminal-wg.pages.freedesktop.org/bidi/ has some excellent notes on how to model bidi in terminal emulators. To make progress, I need to better understand: * what is the bare minimum set of features/level...

There's discussion on https://github.com/kas-gui/kas-text/issues/20 about bidi implementations for Rust. My impression right now is that the state of bidi in Rust is young and that the easiest path will result...

I've pushed a commit with what is probably the bare minimum level of support: I'm sure it's wrong in a number of cases, but with this as my test case...

Thanks James; I'll queue up some more reading/research!