Wez Furlong
Wez Furlong
Hi! Thanks for this! It's a very targeted implementation and it isn't the way I would have thought to do it, which I'll describe below. What I had in mind...
LGTM, thanks!
Thanks for diving in! Can you explain more about what you're trying to resolve here?
There's not enough information here to reproduce or understand what might be happening; what specifically is being output, and in what circumstances are you seeing what happen? When does it...
Please capture a terminal recording: * Launch wezterm. If possible, please use the default terminal size of 80x24 cells as it helps to keep things smaller and easier to manage....
Does this change prevent win32 input mode from being used?
The flags currently in use are borrowed from the usage in the open source windows terminal itself. What I'm concerned about is that without the win32 input mode flag, the...
Could you try building wezterm (or waiting for the windows build to complete in CI and downloading wezterm from the artifacts in the CI run), and give it a quick...
OK, I think this is probably fine. Let's merge it and see if anyone finds an edge case! Thank you!
Please collect some debug info for me by launching wezterm like this, and then pressing the problematic key sequence(s): ``` WEZTERM_LOG=window::os::x11::keyboard=trace,info wezterm -n --config debug_key_events=true ```