VSCodeVIM is unusable (incredibly slow) on larger files, especially in INSERT MODE
<!-- For questions, ask us on [Slack](https://vscodevim-slackin.azurewebsites.net/) 👫. DONT CHANGE ANYTHING UNTIL THE -----. Thanks! --> * Click *thumbs-up* 👍 on this issue if you want it! * Click *confused* 😕 on this issue if not having it makes VSCodeVim unusable. The VSCodeVim team prioritizes issues based on reaction count. -------- **Is this a BUG REPORT or FEATURE REQUEST?** (choose one): **_BUG REPORT_** **Environment**: - **VSCode Version**: **_1.18.1_** (I have tried Insiders build too, and didn't work there either) - **VsCodeVim Version**: **_0.15.5_** - **OS**: **_MacOS High Siera_** **What happened**: When editing longer files, VSCodeVim becomes so slow as to be completely unusable. Typing in insert mode, the keyboard response lags so hard it is impossible to use for anything other than reading files (I've had to switch back to Jetbrains IDE to work on this project in the meantime, since that's the only other IDE I have with a decent VIM plugin). I've included some GIFs below to show this bug in action. Note that I type 100+ WPM, and these videos are in real-time, running at 30FPS. On a <100 line file, typing doesn't seem to have much of a delay:  On a 1-2K line file, typing is already noticeably so slow that it is completely impossible to use: ![1k_line](https://user-images.githubusercontent.com/4033621/33903689-05e07544-df2e-11e7-9c6
Posted by jsonMartin on Dec 12, 2017, 7:23 PM
Tags
Related issues
- To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
- > The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
- Custom trigger IDs are not displayed in the new 2026.10 trigger selector
- I hate that too, but I think it’s more the ux than the concept of a default.
- > The biggest problem with UX developers is they know better than you AND force you into their paradigm.
- "Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
ux (Other)
To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
> The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
Custom trigger IDs are not displayed in the new 2026.10 trigger selector
I hate that too, but I think it’s more the ux than the concept of a default.
> The biggest problem with UX developers is they know better than you AND force you into their paradigm.
"Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
The biggest problem with this is if the target URL doesn't load but also doesn't quickly error out, like e.g.
Google wants to build up a private web here.
VSCodeVIM is unusable (incredibly slow) on larger files, especially in INSERT MODE
<!-- For questions, ask us on [Slack](https://vscodevim-slackin.azurewebsites.net/) 👫. DONT CHANGE ANYTHING UNTIL THE -----. Thanks! --> * Click *thumbs-up* 👍 on this issue if you want it! * Click *confused* 😕 on this issue if not having it makes VSCodeVim unusable. The VSCodeVim team prioritizes issues based on reaction count. -------- **Is this a BUG REPORT or FEATURE REQUEST?** (choose one): **_BUG REPORT_** **Environment**: - **VSCode Version**: **_1.18.1_** (I have tried Insiders build too, and didn't work there either) - **VsCodeVim Version**: **_0.15.5_** - **OS**: **_MacOS High Siera_** **What happened**: When editing longer files, VSCodeVim becomes so slow as to be completely unusable. Typing in insert mode, the keyboard response lags so hard it is impossible to use for anything other than reading files (I've had to switch back to Jetbrains IDE to work on this project in the meantime, since that's the only other IDE I have with a decent VIM plugin). I've included some GIFs below to show this bug in action. Note that I type 100+ WPM, and these videos are in real-time, running at 30FPS. On a <100 line file, typing doesn't seem to have much of a delay:  On a 1-2K line file, typing is already noticeably so slow that it is completely impossible to use: 
No comments yet. Start the discussion.