Spurious OSC 11 command ends up writing to terminal or even executing as commands when opening vim

[downhiller]

Windows Terminal version

1.23.10732.0

Windows build number

10.0.26100.3476

Other Software

I have an issue with 11;rgb:1e1e/1e1e/1e1e;1R sometimes appearing. It's infrequent (once or twice a day). It can happen either when I ctrl-C to cancel a running script, or when launching neovim. The former is no big deal, it just appears as text at my prompt that I can delete. But if it happens when launching vim the effect is to overwrite one character with the letter g (and leave :1e1e/1e1e/1e1e in my command history). This can be incredibly frustrating/damaging if I don't notice at the time.

I think this is an issue with Windows Terminal. I've moved over from PuTTy and never experienced it there.

If it's not a bug per-se, any pointers anyone can give me to fix this would be hugely appreciated!

Steps to reproduce

Open a file in neovim

Expected Behavior

The file opens, unedited

Actual Behavior

The file opens, and a single character will be replaced by a g. Only very occasionally, maybe one in 100 attempts.

[DHowett]

Thanks for reporting!

It looks like this might be a /duplicate of #18004, and may be remediated by changing the escape dwell time.

You can try setting that back to a more sensible value and see if it makes any difference, i.e. add something like set -sg escape-time 500 in your .tmux.conf file.

[downhiller]

But......... I'm not using tmux.

[DHowett]

ARGH, sorry about that!

[DHowett]

The proximal root cause is that vim is requesting a terminal cursor color report. It's weird to me that they're dropping it on the floor when it finally comes back to them...

Can you grab a log via the debug tap?

[downhiller]

Trying now. As I mentioned it only happens occasionally, and easy to miss even when it does. 🤞