Wez Furlong
Wez Furlong
Those artifacts look like junk data in a texture that is mapped into the GPU I've never seen that happen in wezterm before, so I'm suspicious of this being related...
I'm leaning towards calling this a bug in the intel iris/xe opengl implementation on that system
> > * Not all panes are local panes with processes (eg: could be a remote ssh session, or a serial port) so querying the process list will never work...
First look at https://wezfurlong.org/wezterm/config/keyboard-concepts.html#macos-left-and-right-option-key Then if this is still an issue, run through https://wezfurlong.org/wezterm/troubleshooting.html#debugging-keyboard-related-issues and share the information here.
I'll be a bit distracted for the next couple of weeks so I don't have time right now to look at this in detail and make a suggestion, but I...
In the broken scenario, what does the process tree look like, and what does the working process tree look like? wezterm -> cmd -> helix ? wezterm -> wsl ?...
Please try the latest nightly build
This works for me. I suspect there is something else happening in that environment. It might be interesting to strace the wezterm cli process and see what it is getting...
Please try the latest nightly build
I wonder if this is a build issue with libssh on windows, with the consequence that it doesn't quite understand how to load that key?