Using mouse in insert mode causes VIM to think it is in normal mode
See original GitHub issueIs this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
What happened: When in insert mode using the mouse to move the cursor causes the cursor to switch to block and the mode “changes” to normal; however, VIM is actually in insert and as soon as any letter is pressed the mode “switches” to insert and the character(s) are inserted. If the user settings file is open the cursor behaves as expected.
What did you expect to happen: Stay in insert mode, cursor remains a line and moves to clicked location. This happens if the user settings file is open.
How to reproduce it (as minimally and precisely as possible): be in insert mode click anywhere else in the document.
This has also been reported by christiangenco here (Includes a video).
Environment:
- Extension Name: vim
- Extension Version: 0.11.0
- OS Version: Windows_NT x64 10.0.16299
- VSCode version: 1.20.1
{
"activationTimes": {
"startup": true,
"codeLoadingTime": 283,
"activateCallTime": 2,
"activateResolvedTime": 19,
"activationEvent": "*"
}
}
Issue Analytics
- State:
- Created 6 years ago
- Reactions:7
- Comments:10 (3 by maintainers)
Top GitHub Comments
@ivanvoznyakovsky’s bug is happening to me too (and was happening before 0.11.2).
Here’s another video of it happening. Again, strangely, it’s fixed if I open the settings window.
The only key I hit in the video is “a”. When the editor says it’s in “NORMAL” mode and shows a block cursor, it isn’t actually in normal mode, because hitting “a” inserts an “a” character in the second to last position in the line instead of appending.
Here are the plugins and versions I have installed:
I’ve gone back to Atom because of this bug, but I’ll hold out and switch back if it gets fixed 😕
@dmolokanov What you are mentioning is a different issue #5716, it is better fixed with SelectMode that is not implemented yet but is being worked on.
As for the original problem of this issue, I can’t reproduce it and I don’t think it is a problem anymore. So I’m closing this one. But if anyone is still experiencing this issue feel free to comment and we will reopen if needed.