Earlier quoted context omitted.
That was the originally submitted title by Spiritus until a HN mod changed it due to inane policy that the title of the submission must match the title of the webpage.
> due to inane policy that the title of the submission must match the title of the webpage. Not inane, it prevents editorializing, You know the stuff like "Democrats plan to kill more babies" when the Title is "Democrats propose adding more birth control methods".
Newsletter #4 – Thanksvimming Day
31–40 of 40 posts
Re: Newsletter #4 – Thanksvimming Day
#32What 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?
Re: Newsletter #4 – Thanksvimming Day
#33I've been a vim user for a while now, recently started my move over to emacs (evil mode is not bad at all), mostly influenced by the Clojure community. 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?
Re: Newsletter #4 – Thanksvimming Day
#34I've been a vim user for a while now, recently started my move over to emacs (evil mode is not bad at all), mostly influenced by the Clojure community. 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?
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.
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!
Re: Newsletter #4 – Thanksvimming Day
#35Earlier quoted context omitted.
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!
- 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...
Re: Newsletter #4 – Thanksvimming Day
#36Re: Newsletter #4 – Thanksvimming Day
#37Earlier quoted context omitted.
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-…
Re: Newsletter #4 – Thanksvimming Day
#38Re: Newsletter #4 – Thanksvimming Day
#39I've been a vim user for a while now, recently started my move over to emacs (evil mode is not bad at all), mostly influenced by the Clojure community. 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?
Re: Newsletter #4 – Thanksvimming Day
#40Earlier quoted context omitted.
That was months ago actually. I just retried and it works perfectly, but it's still synchronous and blocks the UI. This is what I expect from neovim: provide me with async lint/checks. The only ongoing works on the problem I've seen are https://github.com/scrooloose/syntastic/issues/1253 and https://github.com/benekastah/neomake , which I've not tried yet.
> This is what I expect from neovim: provide me with async lint/checks. It would have to be written using the new remote-plugin architecture I'd think. Plugins that were written for Vim would always be synchronous.
I would guess this feature is already in NeoVim.