-
Notifications
You must be signed in to change notification settings - Fork 36
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
VSCode becomes unresponsive when using VSCodeVim extension and typing < or > #40
Comments
Hi @mboratko , it is hard to take care of different extensions. Each extension could not control what other extension is doing. I suggest you also report this issue to VSCodeVim and VSCode repo. |
@formulahendry absolutely, I understand this interoperability could be challenging. At least for this particular case a partial workaround would be to have an area in the settings which specifies the filetypes that auto rename tag is active for. It was hard to track down this issue, since I assumed auto-rename-tag wouldn't even be active while I was editing a LaTeX document. The reason that wouldn't completely solve the issue, however, is that I do have a need to type LaTeX in HTML documents (via MathJax) so this issue would still show up in that use case. I've filed a bug report with VSCodeVim as well: VSCodeVim/Vim#2214 |
having this same issue, however it occurs when editing html attributes on the same line as the tag and the entire line is past ~80 columns. Editing an attributes on the same line as the tag where the entire line is < ~80 cols works fine. I'm not sure if this is a vim issue or the auto-rename-tags issue |
Steps to reproduce:
Each $B_i$ can be specified by $n$ bits, so we have that the input size is $O(mn)$, and since
$k < n$
(Keystrokes:Esc I $k < n$
)Result:
The cursor freezes after the
<
character, and VSCode is unresponsive. Closing it down leaves a process hanging around in the background, which has to be killed manually. (killall code
)Strangely enough, this does not occur when only one of the two extensions above are installed, but I can't imagine what the connection is. Viscerally, it seemed more related to vscode-auto-rename-tag, due to the opening
<
, so I filed the bug report here.Versions:
The text was updated successfully, but these errors were encountered: