Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regarding the ESC[?4m problem with vim 9 can you update a temporary version first or is there a patch for that? #2016

Open
amaoo opened this issue Dec 14, 2023 · 6 comments
Assignees
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@amaoo
Copy link

amaoo commented Dec 14, 2023

Hello @kingToolbox ,
Currently, many servers have upgraded their VIM version to V9, but there is a problem that ESC[?4m(#1623 (comment)) appears when editing a file, although it can be fixed temporarily by the following ways, but it is always troublesome.

Write these into .vimrc:

set keyprotocol=
let &term=&term
@thiagoojack
Copy link

Thank you!

@pengln
Copy link

pengln commented Aug 14, 2024

This doesn't solve the problem, vim still displays garbled characters.
Dingtalk_20240814094523

@ipenglei466
Copy link

change Term type to vt520
Screenshot from 2024-08-21 14-51-27

@moshangluoying
Copy link

change Term type to vt520 Screenshot from 2024-08-21 14-51-27

only work for a short while.
So troublesome.

@bigplaice
Copy link

add this line in .vimrc

set t_RK=

It works to me.

@kingToolbox kingToolbox self-assigned this Jan 12, 2025
@kingToolbox kingToolbox added bug Something isn't working duplicate This issue or pull request already exists labels Jan 12, 2025
@kingToolbox
Copy link
Owner

Duplicate of #1623

The ESC [?4m control sequence (XTQMODKEYS , Query key modifier options) was introduced in vim 9.0. WindTerm 2.7.0 Prerelease 2 now supports parsing ESC [?4m. Please download and try it. Thank you.

@pengln
It looks like you were launching vi within WSL. WindTerm 2.7.0 Prerelease 2 now uses WinPty instead of ConPty to launch WSL. This change should temporarily address the problem you were experiencing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

7 participants