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

Cannot change to normal mode. #7106

Closed
chris-ryu opened this issue Sep 24, 2021 · 4 comments
Closed

Cannot change to normal mode. #7106

chris-ryu opened this issue Sep 24, 2021 · 4 comments

Comments

@chris-ryu
Copy link

chris-ryu commented Sep 24, 2021

Describe the bug
Once into insert mode, esc key not working then cannot change to normal mode.
When I push esc key in code window, "command 'extension.vim_escape' not found" messeage toasted.
Environment (please complete the following information):

  • Extension (VsCodeVim) version:v1.21.7
  • VSCode version:1.60.2
  • OS: mac OS BigSur 11.6

Additional context
Add any other context about the problem here.
CPU-20210924T021621.449Z.cpuprofile.txt

@tlawren
Copy link

tlawren commented Sep 24, 2021

I might have same or related problem. When switching or adding folders (to workspace), extension stops working and I am stuck in whatever mode I'm I was in. Various commands fail to work and I get errors "command 'extension.vim_<command>' not found"

  • Extension (VsCodeVim) version:v1.21.7
  • VSCode version:1.60.2
  • OS: Windows 10

Current fix is to remove custom vim settings, disable extension, re-enable extension, re-add settings.

@chris-ryu
Copy link
Author

I might have same or related problem. When switching or adding folders (to workspace), extension stops working and I am stuck in whatever mode I'm I was in. Various commands fail to work and I get errors "command 'extension.vim_<command>' not found"

  • Extension (VsCodeVim) version:v1.21.7
  • VSCode version:1.60.2
  • OS: Windows 10

Current fix is to remove custom vim settings, disable extension, re-enable extension, re-add settings.

Thank you.
After delete extensions folder and reinstall extension, It works well

@sethamclean
Copy link

sethamclean commented Oct 7, 2021

This issue is currently happening to me in codespaces. Rebuilding the codespace does not resolve the issue.

Downgrading to 1.21.7 from 1.21.8 resolved the issue.

@elijahrdorman
Copy link

I'll add my issue here too (M1 mac on Monterey).

I blew away everything VS Code related and reinstalled, but escape is still broken

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants