You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, i've been using the vim extension downloaded through the main VScode marketplace (due to proxy issues with the code-server API), but the vim plugin is really slow and a pain to use.
Does everyone else have this problem, or is this due to the vim package in the coder API being slightly different then the marketplace one?
I'm running a setup with over 100 packages. All other ones seem to work flawlessly. Only the vim package is keeping my setup from running on coder. It'd be amazing to see it working at a usable pace
Finally got around to implementing client-side extensions in latest master. 🎉 I'm very interested in hearing any bug reports around that. Currently only vscodevim.vim is white-listed to run in the browser.
Reacted by Jason, Colin Adler, Romulo Alves, Krzysztof Wende and xung
Activity
kylecarbs commentedon Mar 21, 2019
It currently runs on the server. We'll be fixing this by allowing certain exts to run on the client. You can expect this soon.
jakegt1 commentedon Mar 21, 2019
Okay, no worries. Thanks!
wende commentedon Jun 18, 2019
I'm running a setup with over 100 packages. All other ones seem to work flawlessly. Only the vim package is keeping my setup from running on coder. It'd be amazing to see it working at a usable pace
jasonharrison commentedon Aug 4, 2019
The VSCodeVim plugin is rather slow because it listens to all keys and it runs on the server.
Until client-side extensions are ready, https://marketplace.visualstudio.com/items?itemName=jpotterm.simple-vim is a much faster option with some caveats (read the extension's description for a list).
code-asher commentedon Oct 23, 2019
Finally got around to implementing client-side extensions in latest master. 🎉 I'm very interested in hearing any bug reports around that. Currently only
vscodevim.vimis white-listed to run in the browser.jasonharrison commentedon Oct 23, 2019
@code-asher I'm so excited to hear this, can't wait to try it out. Thanks!