Wez Furlong
Wez Furlong
An Investigation into Unresponsiveness and Performance Regression in WezTerm related to Font shaping
Hey, thanks for taking the time to dig into this! If you're in a position to build from source, could you try with this small change to see if not...
Likely a duplicate of: * https://github.com/wez/wezterm/issues/3900
Please try the latest nightly build and let me know if this is still an issue!
the keyboard encoding mode is not at all connected to raw/cooked modes; those are aspects of termios handled by the kernel and have nothing to do with how the terminal...
hmm, I didn't think it is strictly necessary, but sure, I'm ok with enabling it and restoring the original mode when dropped. I think the nuance there is: the probe...
Thanks, can you run wezterm like this: ``` WEZTERM_LOG=window::connection=trace,info wezterm ``` and share what gets logged?
Thanks; so I think this is because the frame is hidden because there are no client-side decorations. I just pushed a really dumb "don't do that" kind of fix for...
I think `main` should behave a little better now; doesn't panic in sway in that way any more.
Please collect some debug info for me by launching wezterm like this, and then pressing the problematic key sequence(s): ```console WEZTERM_LOG=window::os::x11::keyboard=trace,info wezterm -n --config debug_key_events=true ```
This isn't a bug, but an aspect of being a cross-platform application; out of all the systems that wezterm runs on, only fontconfig works this way. The supported way to...