Re:Newsletter #4 – Thanksvimming Day
by CodyReichert on Tuesday November 25, 2014 @03:31PM
(#8659540)
I would say an easier way to create plugins is a pretty big advantage. For some reason I've always been deterred from writing vim plugins, and like you I started using Emacs a few months ago (mostly for the haskell packages), and I feel so much more comfortable writing and editing my own extensions. I've never really looked into neovim, but they're plugin architecture looks really nice so I'll have to check it out.
Nice! did some digging: https://github.com/neovim/neovim/wiki/Plugin-UI-architecture
That's actually pretty nice, was wondering if there are real tools/apps/interfaces out there which are using this as just a POC or a demo.
This is also interesting btw: https://github.com/neovim/python-client will definitely give that a try!
Some plugins that target neovim:
- Floobits: https://github.com/Floobits/floobits-neovim
- Neomake: https://github.com/benekastah/neomake
I recently added neovim support to vim-pandoc. These[1] two lines replaced [2] and [3]. It's quite the improvement.
[1]: https://github.com/vim-pandoc/vim-pandoc/blob/master/pythonx...
[2]: https://github.com/vim-pandoc/vim-pandoc/blob/master/pythonx...
[3]: https://github.com/vim-pandoc/vim-pandoc/blob/master/pythonx...
Nice!
What does neovim do for a not so hardcore user like me who's happy with the current state of affairs? Or in other words, what am I not doing right with vim that I fail to see what neovim offers, apart from a modern code base and may be a better way of writing plugins?