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

Pressing ESC + j or k will equal to Alt + j or k when using Neovim in Windows Terminal #17427

Closed
fanlumaster opened this issue Jun 13, 2024 · 2 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@fanlumaster
Copy link

Windows Terminal version

1.20.11381.0

Windows build number

10.0.22631.0

Other Software

NVIM v0.10.0
Lazyvim v12.13.0

Steps to reproduce

Press esc + j or k at the same time in Insert Mode of Neovim.

Expected Behavior

Back to Normal Mode, and move cursor to next or previous line.

Actual Behavior

Swap current line with next or previous line.

Another issue in other repository that may be helpful: LunarVim/LunarVim#1857

@fanlumaster fanlumaster added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 13, 2024
@carlos-zamora
Copy link
Member

Thanks for filing! We're going to mark this as a /dup of #13792. When it's completed, that'll allow you to work around this issue by encoding ESC+J/K differently.

Copy link
Contributor

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants