Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Newsletter #4 – Thanksvimming Day

neovim.org

Post reply on HN
Print view View original

21–30 of 40 posts

Re: Newsletter #4 – Thanksvimming Day

#21

Post by btipling »

bru wrote: post #19
Spiritus wrote: post #16

Earlier quoted context omitted.

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.

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

Re: Newsletter #4 – Thanksvimming Day

#22

Post by unclesaamm »

Sir_Cmpwn wrote: post #8

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.

Floobits has had a bit of history with unsuccessfully merging an async patch into vim to make their plugin work without breaking leader keys, so this one case isn't too surprising

Re: Newsletter #4 – Thanksvimming Day

#23

Post by brunosutic »

It's great to know neovim development is going strong and there are a lot of contributors making good progress.

I've switched to neovim about a month ago. The installation on OSX is smooth. It's fully functional and all the plugins are working.

Re: Newsletter #4 – Thanksvimming Day

#24

Post by wcunning »

I actually can't get it to build on Fedora 20, at least easily. Not to mention the things I had to figure out to get LinuxBrew working at all. Neovim is not "drop in ready" until it's easy to lay hands on, which basically means packaging for distros.

Re: Newsletter #4 – Thanksvimming Day

#25

Post by Spiritus »

bru wrote: post #19
Spiritus wrote: post #16

Earlier quoted context omitted.

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.

There's a new plugin called neomake[1] which was written from scratch to take advantage of the Neovim async api. It's a young project though.

[1] https://github.com/benekastah/neomake

Re: Newsletter #4 – Thanksvimming Day

#26

Post by voltagex_ »

wcunning wrote: post #24

I actually can't get it to build on Fedora 20, at least easily. Not to mention the things I had to figure out to get LinuxBrew working at all. Neovim is not "drop in ready" until it's easy to lay hands on, which basically means packaging for distros.

What errors did you get?

Re: Newsletter #4 – Thanksvimming Day

#27

Post by Touche »

btipling wrote: post #9
Sir_Cmpwn wrote: post #8

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 problem with this is, unless you are a plugin author these things aren't compelling reasons to switch. Maybe they'll enable new types of plugins not possible before, but until that happens I don't feel a reason to use neovim.

Re: Newsletter #4 – Thanksvimming Day

#28

Post by noir_lord »

davis wrote: post #13
reledi wrote: post #5

Earlier quoted context omitted.

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.

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

Re: Newsletter #4 – Thanksvimming Day

#29

Post by wcunning »

voltagex_ wrote: post #26
wcunning wrote: post #24

I actually can't get it to build on Fedora 20, at least easily. Not to mention the things I had to figure out to get LinuxBrew working at all. Neovim is not "drop in ready" until it's easy to lay hands on, which basically means packaging for distros.

What errors did you get?

Something about libuv or some lua library for libuv not wanting to build. That was after I had to do arcane things to get linuxbrew to recognize my distro's gcc, apparently it's expected to be in /usr/bin/gcc-4.X and Fedora puts it in /usr/bin/gcc.

Re: Newsletter #4 – Thanksvimming Day

#30

Post by lowboy »

davis wrote: post #13
reledi wrote: post #5

Earlier quoted context omitted.

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.

The policy prevents submitter editorializing. It's a good blanket policy, but I think this should be one of the exceptions.

Edit: Now the article has the title "Newsletter #4 - Thanksvimming Day". MODS, ASSEMBLE!!

Post reply on HN