Skip to content
This repository has been archived by the owner. It is now read-only.

vim-mode-next support? #28

Closed
gepoch opened this issue Jul 25, 2015 · 2 comments
Closed

vim-mode-next support? #28

gepoch opened this issue Jul 25, 2015 · 2 comments

Comments

@gepoch
Copy link
Owner

@gepoch gepoch commented Jul 25, 2015

Hey everyone!

We have a lot of vim-mode-next plugins commenting on tickets lately. Currently, it's API is really close to vim-mode. There are no guarantees of this remaining the case, however.

Still, I would love to support it, as long it is within my means to do so! v0.8.0 takes a crack at it. Previously, you could only use vim-surround with vim-mode-next if you had vim-mode installed and disabled.

Now, you don't need the old vim-mode at all.

If the vim-mode-plus API should significantly diverge from vim-mode, and it becomes too much work to maintain API bindings to both, I'll be falling back to vim-mode.

Hopefully, that never happens :)

@bronson
Copy link

@bronson bronson commented Jul 27, 2015

Very cool! I don't picture vim-mode-next ever diverging too much from vim-mode because that would make merging irritating. If you see incompatibilities, tell me, because it's probably a mistake.

Interestingly, with vim-mode's flurry of merged PRs last week, there's not much reason to run vim-mode-next anymore. They're pretty close again. Hope it stays that way, and vim-mode keeps merging PRs quickly. We'll see!

@gepoch gepoch closed this Jan 11, 2016
@bronson
Copy link

@bronson bronson commented Jan 11, 2016

Yes, thank you for closing. I've switched to vim-mode-plus. vim-mode is improving but still has a sizeable PR backlog.

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

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.