My only concern about this is that people are deprecating Vim stuff in favor of NeoVim. My experience with NeoVim is that it's not ready to replace Vim yet - I'm optimistic about NeoVim, but it's too early to start deprecating Vim stuff.
> My experience with NeoVim is that it's not ready to replace Vim yet And when did you last try Neovim? Because I use it everyday with all of my plugins from vim with 0 problems. The new remote plugin system with python support is making huge strides. People have already started on Go support and I imagine JavaScript, lua, etc is not far behind. It's a very exciting time. I recently even got a commit merged, it's a g…
Newsletter #4 – Thanksvimming Day
11–20 of 40 posts
Re: Newsletter #4 – Thanksvimming Day
#12Earlier quoted context omitted.
> My experience with NeoVim is that it's not ready to replace Vim yet And when did you last try Neovim? Because I use it everyday with all of my plugins from vim with 0 problems. The new remote plugin system with python support is making huge strides. People have already started on Go support and I imagine JavaScript, lua, etc is not far behind. It's a very exciting time. I recently even got a commit merged, it's a g…
Thanks for this, i had no idea it was even possible to use NeoVim yet! Think i'll spend some time this holiday setting it up, appreciated!
That's not needed. With the default config or a simple vimrc it's a drop-in replacement. Some extensions don't work yet (even Syntastic) but that should be resolved soon.
Re: Newsletter #4 – Thanksvimming Day
#13It took me a few seconds to realise that "issue" in the title didn't mean "bug report", despite all the other occurrences of it in the article that do.
Same. "Neovim Newsletter #4: Thanksvimming Day" would be a better title.
Re: Newsletter #4 – Thanksvimming Day
#14Re: Newsletter #4 – Thanksvimming Day
#15Earlier quoted context omitted.
Thanks for this, i had no idea it was even possible to use NeoVim yet! Think i'll spend some time this holiday setting it up, appreciated!
>Think i'll spend some time this holiday setting it up, appreciated! That's not needed. With the default config or a simple vimrc it's a drop-in replacement. Some extensions don't work yet (even Syntastic) but that should be resolved soon.
Re: Newsletter #4 – Thanksvimming Day
#16Earlier quoted context omitted.
Thanks for this, i had no idea it was even possible to use NeoVim yet! Think i'll spend some time this holiday setting it up, appreciated!
>Think i'll spend some time this holiday setting it up, appreciated! That's not needed. With the default config or a simple vimrc it's a drop-in replacement. Some extensions don't work yet (even Syntastic) but that should be resolved soon.
Re: Newsletter #4 – Thanksvimming Day
#17My only concern about this is that people are deprecating Vim stuff in favor of NeoVim. My experience with NeoVim is that it's not ready to replace Vim yet - I'm optimistic about NeoVim, but it's too early to start deprecating Vim stuff.
> My experience with NeoVim is that it's not ready to replace Vim yet And when did you last try Neovim? Because I use it everyday with all of my plugins from vim with 0 problems. The new remote plugin system with python support is making huge strides. People have already started on Go support and I imagine JavaScript, lua, etc is not far behind. It's a very exciting time. I recently even got a commit merged, it's a g…
Re: Newsletter #4 – Thanksvimming Day
#18Earlier quoted context omitted.
>Think i'll spend some time this holiday setting it up, appreciated! That's not needed. With the default config or a simple vimrc it's a drop-in replacement. Some extensions don't work yet (even Syntastic) but that should be resolved soon.
So you don't recommend starting fresh?
However there's no difference so far: Syntastic checks are still synchronous, and I should spend some time to research alternatives (e.g. http://www.reddit.com/r/neovim/comments/2m1w3k/neomake_an_as...)
Re: Newsletter #4 – Thanksvimming Day
#19Earlier quoted context omitted.
>Think i'll spend some time this holiday setting it up, appreciated! That's not needed. With the default config or a simple vimrc it's a drop-in replacement. Some extensions don't work yet (even Syntastic) but that should be resolved soon.
I have no problems running Syntastic. What are you running in to?
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.
Re: Newsletter #4 – Thanksvimming Day
#20Is there a usable GUI version of NeoVim yet? (e.g. like MacVim)?