Michael Davis

> Copying with the termcode (OSC52) provider randomly stops working I was able to reproduce this with the same setup. I changed the OSC52 code a bit to do some...

The unicode stuff should be fixed in the latest push - I was accidentally resetting the input/output "code pages" (encodings) after querying for features. That should cover the weird glyphs...

What does your WezTerm config look like?

For better compatibility I switched to the foreground/background sequences suggested in the microsoft docs: https://learn.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences#extended-colors. (As I understand it it's not spec-wise correct but is an idiom used in the...

Is that with the Kitty keyboard protocol enabled? I've seen that behavior with WezTerm as well when it is enabled - termina doesn't seem to get anything from the input...

It looks like this is a bug in the Kitty keyboard encoding function in WezTerm. I sent a patch https://github.com/wezterm/wezterm/pull/6872. I'm not sure why the old encoding causes the key...

That underline behavior may be a bug with WezTerm, I haven't been able to reproduce on Kitty, Alacritty or Foot yet. I'll take a look at how WezTerm is parsing...

I believe that was a different issue with the crossterm backend at the time since I could reproduce it then on different terminals. I added a commit to work around...

Aha, that makes sense, thanks! I'll update this escape to "chunk" the updates so they stay under that conservative limit. If we find lower limits we can tune that further.

Looks like WezTerm just bumped its CSI param limit from 32 to 256: https://github.com/wezterm/wezterm/pull/6194. It's still probably better to keep the number of parameters low for wider compatibility though