4 ms·

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'

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.

btipling 12y ago
> 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 great community and I've plastered my Macbook with Neovim stickers. :P
- fizzbatter 12y ago
  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!
  - bru 12y ago
    >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.
    - fizzbatter 12y ago
      So you don't recommend starting fresh?
      - bru 12y ago
        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_async_make_plugin_syntax_checker/ http://www.reddit.com/r/neovim/comments/2m1w3k/neomake_an_as...)
    - Spiritus 12y ago
      I have no problems running Syntastic. What are you running in to?
      - bru 12y ago
        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 https://github.com/scrooloose/syntastic/issues/1253 and https://github.com/benekastah/neomake https://github.com/benekastah/neomake, which I've not tried yet.
        btipling 12y ago
        > 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.
        kolme 12y ago
        Not necessarily. The original patch Tarruda tried to get merged into Vim provided asynchronous commands in pure Vimscript (through a new kind of event for autocmd). I would guess this feature is already in NeoVim.
        Spiritus 12y ago
        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 https://github.com/benekastah/neomake
- Sir_Cmpwn 12y ago
  The last time I tried it was about two months ago. I'll have to give it another go, thanks!
- Touche 12y ago
  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.
unclesaamm 12y ago
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

btipling 12y ago

> 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 great community and I've plastered my Macbook with Neovim stickers. :P

fizzbatter 12y ago
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!
- bru 12y ago
  >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.
  - fizzbatter 12y ago
    So you don't recommend starting fresh?
    - bru 12y ago
      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_async_make_plugin_syntax_checker/ http://www.reddit.com/r/neovim/comments/2m1w3k/neomake_an_as...)
  - Spiritus 12y ago
    I have no problems running Syntastic. What are you running in to?
    - bru 12y ago
      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 https://github.com/scrooloose/syntastic/issues/1253 and https://github.com/benekastah/neomake https://github.com/benekastah/neomake, which I've not tried yet.
      - btipling 12y ago
        > 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.
        kolme 12y ago
        Not necessarily. The original patch Tarruda tried to get merged into Vim provided asynchronous commands in pure Vimscript (through a new kind of event for autocmd). I would guess this feature is already in NeoVim.
      - Spiritus 12y ago
        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 https://github.com/benekastah/neomake
Sir_Cmpwn 12y ago
The last time I tried it was about two months ago. I'll have to give it another go, thanks!
Touche 12y ago
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.

unclesaamm 12y ago

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