10 ms·

Notable improvements: - Async /Io - Async Jobs - "Packages", which allow easier built-in bundling of plugins I'm pretty excited for this release! I've been

by thedz 10y ago

Notable improvements: - Async /Io - Async Jobs - "Packages", which allow easier built-in bundling of plugins I'm pretty excited for this release! I've been using Neovim for several months now, but really great to see mainline Vim get these (IMO long overdue) enhancements.

desireco42 10y ago
How is Neovim working out for you? I remember using it at one point and it was really smooth experience.
- micku 10y ago
  I'm using it every day for a couple of months now, never crashed and loads faster than Vim 7. Anyway, the things I appreciate more are the fast evolution and the community, no more than one year ago I tried it but was too lazy to compile, wait, configure... This time I ran homebrew, linked my .vimrc in ~/.config/nvim/init.vim, and forgot I was using Neovim instead of Vim, except for the async compiling/linting.
- nobleach 10y ago
  I am stuck at 0.1.3 as I am unable to brew install any of the newer versions. (It craps out on some LuaJIT stuff and I haven't really had time to fight with it) Aside from having to mess with it to get CTRL-h working, it's been pretty smooth. I LOVED vimplug (the package manager) with its async installs. I have high hopes for NeoVim's future... even if that future turns out to be just giving Vim a kick in the pants to move forward.
  - Spiritus 10y ago
    Try cleaning your Homebrew cache for neovim. rm -rf /Library/Caches/Homebrew/neovim--git brew reinstall --HEAD neovim
    - nobleach 10y ago
      nope, sadly: ==> make VERBOSE=1 Last 15 lines from /Users/jimwharton/Library/Logs/Homebrew/neovim/02.make: "__Unwind_GetCFA", referenced from: _lj_err_unwind_dwarf in libluajit.a(lj_err.o) "__Unwind_RaiseException", referenced from: _lj_err_throw in libluajit.a(lj_err.o) "__Unwind_SetGR", referenced from: _lj_err_unwind_dwarf in libluajit.a(lj_err.o) "__Unwind_SetIP", referenced from: _lj_err_unwind_dwarf in libluajit.a(lj_err.o) ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[4]: *** [luajit] Error 1 make[3]: *** [src/luajit] Error 2 make[2]: *** [build/src/luajit-stamp/luajit-install] Error 2 make[1]: *** [CMakeFiles/luajit.dir/all] Error 2 make: *** [all] Error 2 I know I just need to jump into figuring out how to get the ONE version of LuaJIT that works (as I've read, there is only one) and pop that in there.
      - m0shen 10y ago
        Try: unset LUA_CPATH LUA_PATH brew reinstall --HEAD neovim
- thedz 10y ago
  Really great! It was honestly a relatively painless transition for me.
- shazow 10y ago
  Not the parent but FWIW I've been using neovim for +6 months now and it's fantastic. I'm super impressed at the pace of progress and responsiveness of the team. I've since switched all my plugins to use async versions and it's sooo fast, didn't think vim could be faster but here we are.
  - colordrops 10y ago
    Could you mention which plugins you switched to? Is there a list somewhere that details the alternatives that work better in neovim?
    - shazow 10y ago
      Off the top of my head: - vim-plug for a plugin manager (very good regardless of concurrency) - neomake for building - vim-go added async job support using neovim a while ago for most of its functionality, which I use for writing Go My full inventory is here: https://github.com/shazow/dotfiles/blob/master/.vim/plugins.vim https://github.com/shazow/dotfiles/blob/master/.vim/plugins....
      - kzrdude 10y ago
        Do most vim plugins work without changes in neovim? I'm mostly using vim-airline and tagbar to be honest, wouldn't be sad if the other ones stopped working.
        hsitz 10y ago
        VimScript is not deprecated in NeoVim, and maintaining backward compatibility is major focus. So must Vim plugins will work in Neovim. vim-airline is listed among the plugins that has some special neovim-specific features added: https://github.com/neovim/neovim/wiki/Related-projects https://github.com/neovim/neovim/wiki/Related-projects
        kzrdude 10y ago
- cyphar 10y ago
  I've been using neovim for almost a year now, and have contributed some (small) code fixes and also donate to the project. It works great for me, and I completely forget that I'm using neovim (until I use :terminal). Also, from what I hear, contributing to Vim is much harder than NeoVim so I'm more inclined to contribute to a project which has a healthy community of contributors.
- fatbird 10y ago
  I switched more than a year ago and have never had stability problems; it's been only performance and feature enhancements for me. The most obvious was that saving my files no longer locked up the interface for a couple seconds while linters ran (thank you async). More subtly, I had to go on a plugin diet initially that slimmed my features down to what I actually used regularly; since then, I judge the quality of plugins to be improved because they're either new plugins by authors excited to code for neovim, or they're current plugins that got a decent overhaul to work with both. From what I understand, the plugin community is generally pretty happy with neovim and find it preferable.
vegabook 10y ago
this async thing was Neovim's main selling point, right? I mean cruft-removal is all well and good but vim works fast and fine for me so not important. What does Neovim now offer that this doesn't?
- jpambrun 10y ago
  I think neovim just offered us VIM 8.0.
  - baldfat 10y ago
    To be fair VIM developers have said they were all in the mix and coming. We even had Vim plug ins that pulled this off. So I really am not surprised.
- dominotw 10y ago
  'transform Vim into an embeddable text editor engine' I think that was the main objective of the project. Would be nice to real vim in IntelliJ idea.
  - micku 10y ago
    This. And the scripting language I suppose?
  - stephenboyd 10y ago
    As a naive IntelliJ user, I found myself editing files with Vim in IntelliJ's terminal console.
    - dominotw 10y ago
      whoa! had no idea this was thing .
    - weitzj 10y ago
      I was amazed when I discovered the console and everything works. I can launch vim, neovim and tig(nurses git front-end) from within IntelliJ and all shortcuts just work. Even fish shell in vi mode or tmux. So yeah, I have the shell running in IntelliJ with tmux enabled and launch tig inside of it.
agumonkey 10y ago
lambdas and closure .. and vim/neovim split .. almost Emacs ;)
- dleslie 10y ago
  Soon NeoVim will no longer update regularly because Vim has caught up and/or surpassed it with every feature that matters... By that time Emacs will have replaced temacs with Guile and someone clever will have added VimScript as a hosted language.
  - agumonkey 10y ago
    The neovim project is still a massive undertaking about refactoring such old and non trivial piece of code in what appears to be a smooth way. I hope they can keep working on it, in symbiosis with vim.
  - mden 10y ago
    It's close, but I think NeoVim's RPC model could be huge. Writing a new frontend for vim no longer seems that crazy of a goal which makes it easier for people to experiment with new editor ideas while relying on the very solid core of vim (well at least I find that exciting, idk if the general vimmer cares).
    - romgrk 10y ago
      https://www.youtube.com/watch?v=TI5azVeDUDo https://www.youtube.com/watch?v=TI5azVeDUDo
    - wodenokoto 10y ago
      I dream of the day that when you tick off "vim binding" in the settings of any IDE it loads neovim for controlling the buffer.
      - yazaddaruvala 10y ago
        Or rather, a day where its easier, more flexible, and more performant for IDEs to always(only) use an embedded neovim. Getting plugin support "for free". The keybindings would then be the only thing that the IDE changes.
deleted 10y ago
[deleted]
JoshTriplett 10y ago
I'd love to see vim add an embedded terminal emulator in a window based on the async support. That feature alone motivated me to try neovim.
- joemi 10y ago
  That feels like the realm of a plugin, IMO. (I don't know enough to know whether or not that type of thing could be done via plugin, though.)
  - flukus 10y ago
    With the new async support it should be relatively simple, weekend project simple for a basic implementation.
    - JoshTriplett 10y ago
      Depends on how you implement it. neovim's implementation uses libvterm, which seems preferable to a from-scratch terminal implementation. Implementing a fully capable terminal emulator from scratch definitely isn't a weekend project. neovim's approach links libvterm in via C. You could potentially do so via python and ctypes instead, but then you have to count on having a vim compiled with Python support.
      - flukus 10y ago
        I was thinking I'd just start sh/cmd in a process and use stdin/stdout. The api even allows for automatically sending appended lines to stdin.
- allendoerfer 10y ago
  That is tmux's job. Do one thing well.
  - deathanatos 10y ago
    I use ConqueTerm, inside vim, a plugin that supplies a terminal inside Vim. If you put the emulator inside the editor, you can take advantage of vim's extremely capable text manipulation. If I tmux then vim, I have to find some way to get the text out of tmux, and then back into vim. Also, who says vim is running in a terminal?

by thedz 10y ago

desireco42 10y ago

How is Neovim working out for you? I remember using it at one point and it was really smooth experience.

micku 10y ago
I'm using it every day for a couple of months now, never crashed and loads faster than Vim 7. Anyway, the things I appreciate more are the fast evolution and the community, no more than one year ago I tried it but was too lazy to compile, wait, configure... This time I ran homebrew, linked my .vimrc in ~/.config/nvim/init.vim, and forgot I was using Neovim instead of Vim, except for the async compiling/linting.
nobleach 10y ago
I am stuck at 0.1.3 as I am unable to brew install any of the newer versions. (It craps out on some LuaJIT stuff and I haven't really had time to fight with it) Aside from having to mess with it to get CTRL-h working, it's been pretty smooth. I LOVED vimplug (the package manager) with its async installs. I have high hopes for NeoVim's future... even if that future turns out to be just giving Vim a kick in the pants to move forward.
- Spiritus 10y ago
  Try cleaning your Homebrew cache for neovim. rm -rf /Library/Caches/Homebrew/neovim--git brew reinstall --HEAD neovim
  - nobleach 10y ago
    nope, sadly: ==> make VERBOSE=1 Last 15 lines from /Users/jimwharton/Library/Logs/Homebrew/neovim/02.make: "__Unwind_GetCFA", referenced from: _lj_err_unwind_dwarf in libluajit.a(lj_err.o) "__Unwind_RaiseException", referenced from: _lj_err_throw in libluajit.a(lj_err.o) "__Unwind_SetGR", referenced from: _lj_err_unwind_dwarf in libluajit.a(lj_err.o) "__Unwind_SetIP", referenced from: _lj_err_unwind_dwarf in libluajit.a(lj_err.o) ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[4]: *** [luajit] Error 1 make[3]: *** [src/luajit] Error 2 make[2]: *** [build/src/luajit-stamp/luajit-install] Error 2 make[1]: *** [CMakeFiles/luajit.dir/all] Error 2 make: *** [all] Error 2 I know I just need to jump into figuring out how to get the ONE version of LuaJIT that works (as I've read, there is only one) and pop that in there.
    - m0shen 10y ago
      Try: unset LUA_CPATH LUA_PATH brew reinstall --HEAD neovim
thedz 10y ago
Really great! It was honestly a relatively painless transition for me.
shazow 10y ago
Not the parent but FWIW I've been using neovim for +6 months now and it's fantastic. I'm super impressed at the pace of progress and responsiveness of the team. I've since switched all my plugins to use async versions and it's sooo fast, didn't think vim could be faster but here we are.
- colordrops 10y ago
  Could you mention which plugins you switched to? Is there a list somewhere that details the alternatives that work better in neovim?
  - shazow 10y ago
    Off the top of my head: - vim-plug for a plugin manager (very good regardless of concurrency) - neomake for building - vim-go added async job support using neovim a while ago for most of its functionality, which I use for writing Go My full inventory is here: https://github.com/shazow/dotfiles/blob/master/.vim/plugins.vim https://github.com/shazow/dotfiles/blob/master/.vim/plugins....
    - kzrdude 10y ago
      Do most vim plugins work without changes in neovim? I'm mostly using vim-airline and tagbar to be honest, wouldn't be sad if the other ones stopped working.
      - hsitz 10y ago
        VimScript is not deprecated in NeoVim, and maintaining backward compatibility is major focus. So must Vim plugins will work in Neovim. vim-airline is listed among the plugins that has some special neovim-specific features added: https://github.com/neovim/neovim/wiki/Related-projects https://github.com/neovim/neovim/wiki/Related-projects
        kzrdude 10y ago
cyphar 10y ago
I've been using neovim for almost a year now, and have contributed some (small) code fixes and also donate to the project. It works great for me, and I completely forget that I'm using neovim (until I use :terminal). Also, from what I hear, contributing to Vim is much harder than NeoVim so I'm more inclined to contribute to a project which has a healthy community of contributors.
fatbird 10y ago
I switched more than a year ago and have never had stability problems; it's been only performance and feature enhancements for me. The most obvious was that saving my files no longer locked up the interface for a couple seconds while linters ran (thank you async). More subtly, I had to go on a plugin diet initially that slimmed my features down to what I actually used regularly; since then, I judge the quality of plugins to be improved because they're either new plugins by authors excited to code for neovim, or they're current plugins that got a decent overhaul to work with both. From what I understand, the plugin community is generally pretty happy with neovim and find it preferable.

vegabook 10y ago

this async thing was Neovim's main selling point, right? I mean cruft-removal is all well and good but vim works fast and fine for me so not important. What does Neovim now offer that this doesn't?

jpambrun 10y ago
I think neovim just offered us VIM 8.0.
- baldfat 10y ago
  To be fair VIM developers have said they were all in the mix and coming. We even had Vim plug ins that pulled this off. So I really am not surprised.
dominotw 10y ago
'transform Vim into an embeddable text editor engine' I think that was the main objective of the project. Would be nice to real vim in IntelliJ idea.
- micku 10y ago
  This. And the scripting language I suppose?
- stephenboyd 10y ago
  As a naive IntelliJ user, I found myself editing files with Vim in IntelliJ's terminal console.
  - dominotw 10y ago
    whoa! had no idea this was thing .
  - weitzj 10y ago
    I was amazed when I discovered the console and everything works. I can launch vim, neovim and tig(nurses git front-end) from within IntelliJ and all shortcuts just work. Even fish shell in vi mode or tmux. So yeah, I have the shell running in IntelliJ with tmux enabled and launch tig inside of it.

agumonkey 10y ago

lambdas and closure .. and vim/neovim split .. almost Emacs ;)

dleslie 10y ago
Soon NeoVim will no longer update regularly because Vim has caught up and/or surpassed it with every feature that matters... By that time Emacs will have replaced temacs with Guile and someone clever will have added VimScript as a hosted language.
- agumonkey 10y ago
  The neovim project is still a massive undertaking about refactoring such old and non trivial piece of code in what appears to be a smooth way. I hope they can keep working on it, in symbiosis with vim.
- mden 10y ago
  It's close, but I think NeoVim's RPC model could be huge. Writing a new frontend for vim no longer seems that crazy of a goal which makes it easier for people to experiment with new editor ideas while relying on the very solid core of vim (well at least I find that exciting, idk if the general vimmer cares).
  - romgrk 10y ago
    https://www.youtube.com/watch?v=TI5azVeDUDo https://www.youtube.com/watch?v=TI5azVeDUDo
  - wodenokoto 10y ago
    I dream of the day that when you tick off "vim binding" in the settings of any IDE it loads neovim for controlling the buffer.
    - yazaddaruvala 10y ago
      Or rather, a day where its easier, more flexible, and more performant for IDEs to always(only) use an embedded neovim. Getting plugin support "for free". The keybindings would then be the only thing that the IDE changes.

deleted 10y ago

[deleted]

JoshTriplett 10y ago

I'd love to see vim add an embedded terminal emulator in a window based on the async support. That feature alone motivated me to try neovim.

joemi 10y ago
That feels like the realm of a plugin, IMO. (I don't know enough to know whether or not that type of thing could be done via plugin, though.)
- flukus 10y ago
  With the new async support it should be relatively simple, weekend project simple for a basic implementation.
  - JoshTriplett 10y ago
    Depends on how you implement it. neovim's implementation uses libvterm, which seems preferable to a from-scratch terminal implementation. Implementing a fully capable terminal emulator from scratch definitely isn't a weekend project. neovim's approach links libvterm in via C. You could potentially do so via python and ctypes instead, but then you have to count on having a vim compiled with Python support.
    - flukus 10y ago
      I was thinking I'd just start sh/cmd in a process and use stdin/stdout. The api even allows for automatically sending appended lines to stdin.
allendoerfer 10y ago
That is tmux's job. Do one thing well.
- deathanatos 10y ago
  I use ConqueTerm, inside vim, a plugin that supplies a terminal inside Vim. If you put the emulator inside the editor, you can take advantage of vim's extremely capable text manipulation. If I tmux then vim, I have to find some way to get the text out of tmux, and then back into vim. Also, who says vim is running in a terminal?