Skip to content
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.

VSCode compatibility #206

Closed
HaleTom opened this issue Dec 21, 2021 · 4 comments
Closed

VSCode compatibility #206

HaleTom opened this issue Dec 21, 2021 · 4 comments

Comments

@HaleTom
Copy link

HaleTom commented Dec 21, 2021

I'm trying to select a jump-movement plugin.

How well does this one work with VSCode?

@yashlala
Copy link

yashlala commented Jan 9, 2022

I'm a bit confused -- this plugin is for neovim only, not VSCode.

Are you embedding neovim in VSCode somehow?

@HaleTom
Copy link
Author

HaleTom commented Jan 9, 2022

Yes, I am using that VSCode plugin.

There is https://github.com/asvetliakov/vim-easymotion which fixes EasyMotion's buffer changing issues to work with VSCode.

Does this plugin also works with VSCode via asvetliakov/vscode-neovim or other such embedding plugin?

@hadronized
Copy link
Owner

I have no idea, never tried that plugin. If you use a plugin that goes through neovim inside VS Code I « guess » it should work, but it depends on how that plugin supports the Neovim API I guess.

@ibehnam
Copy link

ibehnam commented Dec 8, 2022

This is my question too. Many devs use VSCode Neovim extension. So far, Leap and Lightspeed work well on VSCode, but Hop hasn't been working so far :/

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants