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
Environment:
VSCode Version: 1.17.2
VsCodeVim Version: 0.10.2
OS: OS X El Capitan 10.11.6
What happened:
Start typing a closing tag and let Auto Close Tag trigger drop down of autocompletions. Eg, Type
<v-dialog></...
The options will show in a drop down but then VSCode becomes immediately unresponsive. I bring up Mac's Activity Monitor and see "Code Helper" at 99% CPU. Force quitting Code Helper alleviates the issue but it will happen each time you reproduce the steps.
Auto Close Tag works fine withVSCodeVim plugin disabled.
What did you expect to happen:
Using VSCodeVim and Auto Close Tag plugin to work together without crashing VSCode.
How to reproduce it:
Install VSCodeVim and Auto Close Tag plugins. Open an HTML file and type any HTML tag and then start typing its corresponding closing tag. Let autocomplete options show and observe activity monitor for CPU usage.
michael-land
commented
6 years ago
The VSCodeVim team prioritizes issues based on reaction count.
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG Environment:
What happened:
Start typing a closing tag and let Auto Close Tag trigger drop down of autocompletions. Eg, Type
<v-dialog></...The options will show in a drop down but then VSCode becomes immediately unresponsive. I bring up Mac's Activity Monitor and see "Code Helper" at 99% CPU. Force quitting Code Helper alleviates the issue but it will happen each time you reproduce the steps.
Auto Close Tag works fine withVSCodeVim plugin disabled.
What did you expect to happen: Using VSCodeVim and Auto Close Tag plugin to work together without crashing VSCode.
How to reproduce it: Install VSCodeVim and Auto Close Tag plugins. Open an HTML file and type any HTML tag and then start typing its corresponding closing tag. Let autocomplete options show and observe activity monitor for CPU usage.