-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Vim extension is not working after installation #61
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
Comments
Should work once we release 1.31.1. Should release tomorrow |
Thanks! |
Just upgraded to v1.31.1-100, but the vim extension is still not working |
We likely have to re-fetch the Vim extension. Likely will occur within ~12hrs. cc: @foresthoffman |
I'm hitting the same problem like this (vim plugin v1.1.0) in v1.31.1-100. I think this issue has relation to it.
I try to downgrade vim version, but I don't know how to do. #77 |
Hmm the suggested fix was to upgrade to v1.31.1, but since that isn't doing the trick, i'll try downgrading vim. Will respond with an update soon. |
v1.0.8 of vscodevim seems to work with v1.31.1. Will push the downgraded version. |
@foresthoffman was it pushed? |
We seem to have updated VSCode which I believe was the problem. #117 |
@nhooyr Yes, I had to make some changes to prevent rolling the version forward before VSCode removes negative look behinds. v1.0.8 of VSCodeVim.Vim should refresh and be functional in about an hour. |
Vim was fixed over the weekend, should be good to go! |
I seem to be getting this error
|
Like me, Did you find a solution? |
That error has been fixed but it's not in a release yet. Should have one
out today.
|
@code-asher did this fix end up in a release? |
It did, check out the latest (2.1698). Keep in mind Chrome is still the
only supported browser since the Vim extension uses regular expressions
not supported by Firefox and Safari.
|
Hey, there. This problem seems to have resurfaced. VSCodeVIM versions 1.13.0 and 1.13.1 do not work with code-server 2.1698-vsc1.41.1 or 3.0.1 |
@AlbertDeFusco Are you getting the same message shown below in the browser's developers console? |
@chaopli Can you reproduce? If so, could you reopen the issue? |
@AlbertDeFusco @vnijs I've experienced the same issue. I believe it may be related to VSCodeVim/Vim#4173 Regardless, downgrading to VSCodeVIM version 1.12.4 fixed the issue for me. 1.12.4 can be installed from the code-server extension marketplace directly. |
Nice @cmoog |
Downgrading to 1.12.4 did not help for me on |
Also please file a new issue if still doesn't work installing from our marketplace. |
code-server
version: 1.31.0-20Steps to Reproduce
The text was updated successfully, but these errors were encountered: