I’ve really wanted to write a Kakoune style layer for VS Code or even a Kakoune style editor that works natively on Windows.
Show HN: Build your own Vim emulation for VS Code
41–50 of 51 posts
Re: Show HN: Build your own Vim emulation for VS Code
#42Re: Show HN: Build your own Vim emulation for VS Code
#43Earlier quoted context omitted.
I don't mean to disparage it. Apologies if my post came off that way. I certainly appreciate it and understand emulating vim is not an easy task.
Yeah, I was thinking I may have been a bit aggro there. It's just a coincidence that I only recently embraced IDE life (finally!), and it's in no small part because of this extension. Cheers.
Re: Show HN: Build your own Vim emulation for VS Code
#44Earlier quoted context omitted.
For those that are unaware, it’s literally the same system underneath. Vscode talks to language servers to do all the work and they’ve architected the system in such a way that others can talk to them too. Coc.vim provides the plumbing to do that from vim. It’s a great project. Took me a while to get things configured properly but it’s been great for doing all my typescript work.
Is anyone aware of an 'opinionated' neovim distribution? Something like spacemacs or Emacs Live, that takes care of all the configuration work to give a solid basis out of the box. I've been dragging my feet on switching everything to nvim because I don't have 'awhile to get things configured properly' these days.
Re: Show HN: Build your own Vim emulation for VS Code
#45It's disappointing to see from comments here that there's no true and performant Vim integration for VS Code. It used to be the same thing with Eclipse and JetBrain's IDEs. Whatever Vim plugins existed were slow and falling into the uncanny valley, where they lacked support for many features or did things in slightly unexpected ways. Torn between Vim and effectively Vimless IDEs, I chose to stick to the former and do…
i had to switch to go/java for work and this has worked better for me than simply writing everything in vim - although vim-go is great, i enjoy being able to run and debug my tests and code in intellij.
Re: Show HN: Build your own Vim emulation for VS Code
#46Re: Show HN: Build your own Vim emulation for VS Code
#47This is an interesting approach. I find the popular vim emulation extension (vscodevim) is a bit buggy and has lots of "uncanny valley" gaps. At work I use vscodevim, and at home I use vim with TypeScript plugins. Both approaches have lots of annoyances. Maybe a weekend dedicated to ModalEdit could give me the experience I'm really after. I'm also excited for Oni Vim 2, which is a commercial product who's promise is…
One of the most annoying thing with this extension is that it maintain a different revert history that is conflicting with the normal one. Sometimes you just have to close a file without saving it because undo/redo is broken. And it's extremely slow on medium to large files and it gets slower and slower until you restart vscode. I have a love hate relationship with this extension. It's terrible but vscode without it…
Re: Show HN: Build your own Vim emulation for VS Code
#48Re: Show HN: Build your own Vim emulation for VS Code
#49This is an interesting approach. I find the popular vim emulation extension (vscodevim) is a bit buggy and has lots of "uncanny valley" gaps. At work I use vscodevim, and at home I use vim with TypeScript plugins. Both approaches have lots of annoyances. Maybe a weekend dedicated to ModalEdit could give me the experience I'm really after. I'm also excited for Oni Vim 2, which is a commercial product who's promise is…
One of the most annoying thing with this extension is that it maintain a different revert history that is conflicting with the normal one. Sometimes you just have to close a file without saving it because undo/redo is broken. And it's extremely slow on medium to large files and it gets slower and slower until you restart vscode. I have a love hate relationship with this extension. It's terrible but vscode without it…
Sounds kind of weird now that I’ve put it in writing. It works for me but YMMV.