Live data from Hacker News

Newsletter #4 – Thanksvimming Day

neovim.org

11–20 of 40 posts

Re: Newsletter #4 – Thanksvimming Day

#11
post #9

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…

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!

Re: Newsletter #4 – Thanksvimming Day

#12
post #9

Earlier 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!

>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

#13
post #5

It 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.

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.

Re: Newsletter #4 – Thanksvimming Day

#15
post #12

Earlier 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.

So you don't recommend starting fresh?

Re: Newsletter #4 – Thanksvimming Day

#16
post #12

Earlier 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.

I have no problems running Syntastic. What are you running in to?

Re: Newsletter #4 – Thanksvimming Day

#17
post #9

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…

The last time I tried it was about two months ago. I'll have to give it another go, thanks!

Re: Newsletter #4 – Thanksvimming Day

#18
post #12

Earlier 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?

Do keep in mind that my experience is really limited: I compiled neovim and it works fine with my .vimrc & all extensions. So there's no reason to start 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

#19
post #12

Earlier 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?

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.

Post reply on HN