Wez Furlong

I think having some methods (and corresponding key assignment actions) like these would be nice: * `pane:screenshot(filename)` - save as png * `pane:start_recording(filename, [fps, format])` * `pane:stop_recording()` (I don't want...

I looked at this a bit yesterday; it's currently blocked because EGL doesn't seem to be compatible with the apis that read pixel buffers. Need to figure this out.

@JPHutchins thanks for the tip. Docs seems to be a weak point right now, but it sounds potentially interesting!

Yes, as stated above, this is resolved in the nightly build. Continuing to try to use the prior release build which MS refuse to reclassify is just adding noise here.

FWIW, the implementation of Sixel, iTerm2 and Kitty Image protocols in wezterm map the incoming image into texture coordinates on cells in the display; those cells reference the same "atomic"...

From zero -> iTerm2 wasn't all that difficult, and I like its relative simplicity compared to the other protocols. I think the biggest potential stumbling block was allowing for arbitrary...

From my perspective in implementing images in wezterm (both sixel and iterm2), and thinking only about images, rather than text+images, modeling 3 vs. arbitrary layers isn't especially different (fixed size...

OK, so my mental model for this is that each cell has a textual z-axis layer number (default 0) and that it can have essentially a list of attachments; each...

FWIW, I don't see that additional layers means massively increasing the storage requirements. The spec talks about uploading an image, and then separately placing it in the model. That placement...

I don't have bandwidth for this directly, but you could potentially leverage https://github.com/wez/wezterm/blob/main/.github/workflows/pages.yml which is the action I use to publish the wezterm docs to gh_pages using mdbook. I don't...