Wez Furlong
Wez Furlong
re: multiple issues, the problem there is that most people are (phrasing this charitably!) too busy to search to find the matching issue. I'm dramatically outnumbered by users and don't...
Likely a duplicate of: * https://github.com/wez/wezterm/issues/1983 * https://github.com/wez/wezterm/issues/3396 * https://github.com/wez/wezterm/issues/3575
Please try the latest nightly build and let me know if this is still an issue!
Is this working in the latest release? If not, please update the debug output: ``` WEZTERM_LOG=window::os::x11::keyboard=trace,info wezterm -n --config debug_key_events=true ```
I think 15da2e64c27b282d55708d6514dd8aa0040cc7d4 would resolve this, but the scoping of it is tricky; see #4933 for where it unintentionally changes how a keypress is encoded--that particular issue is not really...
is this on an external monitor?
Please try the latest nightly build and let me know if this is still an issue!
I'm not clear on when the issue triggers now; could you clarify what is needed for it to occur now?
I just haven't had time to review this
FWIW, wezterm does support using shm with the kitty protocol.