Wez Furlong

I'm not sure what can be done to improve this with flatpaks, so for the moment, I've added a note about flatpak limitations to the install section of the docs.

Activating a window with the intent of switching workspace is a bit thorny because you're really wanting to control the GUI (which is what owns the GUI window -> Mux...

We can keep it open for a bit; I may decide to close it later, or I may figure out a way to make this work nicely.

FWIW, I prefer to track feature requests as enhancement issues, because the issue management interface cannot include discussions, so they effectively vanish when I'm triaging and reviewing the backlog.

Implementation wise, I think this would be done similarly to https://wezfurlong.org/wezterm/config/lua/window/set_right_status.html, but scoped to the pane instead of the window. https://wezfurlong.org/wezterm/config/lua/window-events/update-status.html could be used to determine when to call/update the...

> _behind_ the text, Because the pane renderer produces opaque renderings (by default, unless the user has taken care to render with opacity), that would require interleaving the display logic...

What does `nvidia-smi` show as the graphic memory usage for wezterm? Do you use any image protocols in your workflow?

I've made some adjustments to help keep the memory usage bounded better. Please give the nightly build a try in about an hour. If you find that the usage is...

I've made a couple of improvements to cache efficiency that may help here; I'd appreciate it if you could try a852e47dba2bf576b226b95ee1a329887a354e2a which should show up as a nightly build soonish....

See also: https://github.com/wez/wezterm/issues/3815