-
Notifications
You must be signed in to change notification settings - Fork 110
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
Question: Any plans to port this to VSC? #1063
Comments
Currently no. But I think if you think vmp is better tha VsCodeVim, putting that impression to them might lead them to do more research on vmp. Which is very honor to me as one vim-plugin author among tons of similar projects. |
This has been the best vim implementation I have ever used. I believe this particular vim implementation should be abstracted so that it can be consumed on any JS based editor. I keep atom around for the sheer power and productivity. Thanks @t9md for this gift! |
Thanks, and what you've suggested is just jordan suggested long before. Theoretically it's possible, and what vmp shines is each operator/motion is very declaratively defined which might make editor-agnostic abstraction easy. |
The problem with VS Code (and unfortunately with VS Code Vim) is that there's not enough information in the public API to enable a fully compatible (or even as good as atom's) vim extension. See microsoft/vscode#22276 (comment) for more details on this. Because of the architecture of VS Code, extensions cannot know some of the things the core does. I agree it would be cool if vim-mode-plus were editor agnostic, but I don't think VS Code will (soon, or maybe ever) support all the API needed to do it. |
This is a very good discussion. For me, it would be better to use vscode as scala integration is better. But, vmp is so good that it keeps me firmly in Atom Thanks @t9md for the best vim emulation I've used |
VMP is a beast. I'm totally hooked. Thank you @t9md for producing this excellent software. With Facebook shutting down nuclide and Atom-IDE, and with VSCode growing in popularity, I'm worried that a day might come in the future when atom is no longer relevant, and I'll have to give up on I hope work on abstracting the core of VMP will succeed so that many more users can enjoy these features. |
Oh, I didn’t know FB shut down nuclide. |
Yeah, I'd switch to xray in a heartbeat if it's as fast as what's out there make it seem. It would be the best of atom and sublime text. I don't think atom will be shut down any time soon, per the community manager, Lee: https://discuss.atom.io/t/the-microsoft-intervention/55744 If it does get shut down, I hope VS Code will be able to support all the cool features of VMP that aren't in vscodevim
|
Lack of subword movements in VSCode is so critical for me, as well as occurrences. But I personally have no choice because I work a lot with TypeScript recently and VSCode works just flawlessly with it. Would love to see VMP ported to VSCode ❤️ |
@t9md, Github has decided not to move forward on x-ray in any capacity 😞 |
Is that Atom's activity? |
so love you |
Note for anyone coming here from Google, if you have atom-ide-ui and atom-ide-typescript, but not atom-typescript installed, you can bind 'atom-text-editor.vim-mode-plus.normal-mode':
'g d': 'hyperclick:confirm-cursor'
'g h': 'datatip:toggle' |
this might be of interest to the discussion |
Also of interest is https://github.com/asvetliakov/vscode-neovim which bypasses |
For what it's worth, github announced the sunsetting of Atom: https://github.blog/2022-06-08-sunsetting-atom/ |
@keevan Thank you for sharing this. It is sad. very sad. |
Indeed. Thanks so much for creating this plugin though, it was by far the best Vim integration I've used in any editor/IDE by far. Atom + vim-mode-plus will be missed. The bright side is that some Atom devs are working on a new editor called Zed (https://zed.dev). Hoping that will be a good successor |
I would like to have this available in Visual Studio Code. There is a Vim emulation extension but it seems to be missing some features I enjoy in this package.
The text was updated successfully, but these errors were encountered: