12 ms·

NeoVim 0.2.0 released

• oblio 9y ago
  My God, it's full of stars :) > Windows support: > Windows is no longer "experimental", it is fully supported. > Windows package includes a GUI, curl.exe and other utilities.
  • kuon 9y ago
    Wasn't "dev moving away from macOS" a hot topic on HN lately?
    • oblio 9y ago
      It was, but I'm on Windows, so no "moving away from MacOS" for me, anyway :)
• shakna 9y ago
  > This release features a macOS pre-built package. Yay, no more compiling to upgrade! > Windows is no longer "experimental", it is fully supported. > Windows package includes a GUI, curl.exe and other utilities. Awesome. Well thought-out. > 1215084 backtick-expansion works with shell=fish #6224 Solves one of my main problems.
  • petre 9y ago
    Should be an app/dmg though. The libs shipped with it can interfere with my setup.
• adrianN 9y ago
  I'm currently using vim and I'm quite happy with it. I don't use many plugins, so better support for plugins is not very helpful to me. Are there other reasons why I should switch to Neovim?
  • oblio 9y ago
    For your use case, probably not many reasons. Maybe the built in terminal?
    • andyhoang 9y ago
      What good of a built in terminal? Thanks
      • oblio 9y ago
        I'm not sure I understood your question. This is the terminal: https://neovim.io/doc/user/nvim_terminal_emulator.html https://neovim.io/doc/user/nvim_terminal_emulator.html If you're asking what good is a built in terminal, well, there's plenty of scenarios. One I'm facing right now is using GVim on Windows. Have you ever seen what happens when you type !dir in GVim, right now? It's really ugly.
      • gkya 9y ago
        In Emacs the shell-mode allow me to use the shell as any other buffer, with random access and scrolling. I can cut and paste stuff just like in any other text buffer, manipulate the output of my session to save it to some file / send it to someone else, etc. IDK how it is in nvim but I'm quite pleased with shell in Emacs, can't go back at all. Though if you're using tmux or maybe screen you can probably do similar things.
        • oblio 9y ago
          The Vim :sh is much more limited. I actually kind of stopped using it a while ago because it the workflow was so jarring, especially on Windows. Neovim's :terminal is from what I can tell more or less equivalent to Emacs's shell.
      • saturn_vk 9y ago
        I don't use it as a terminal. However, it makes things like fzf integrate quite nicely with neovim. The later looks and interacts awfully in vim.
• mikaelj 9y ago
  Hope someone (not me!) starts working on a nvimclient (akin to emacsclient) soon.
  • rjzzleep 9y ago
    maybe neovim-remote is what you want? https://github.com/mhinz/neovim-remote https://github.com/mhinz/neovim-remote
    • mikaelj 9y ago
      Close, but not enough. I want to open the same editor session spread across multiple windows on multiple monitors.
      • asymmetric 9y ago
        Can't you do that with tmux?
        • mikaelj 9y ago
          No, Vim can only have one buffer active at any given time.
      • sevensor 9y ago
        I saw this thread, and I promised myself I wasn't going to plug Kakoune -- I think NeoVim is a great project and I want it to succeed. They deserve every bit of the praise they're getting. But I'm going to have to break my promise, because Kakoune has the exact feature you're after, and I'm using it right now. That, along with familiar keybindings, selection-oriented modal interface, tmux integration... I could go on. Kakoune is a modern modal text editor for your terminal, and it's worth trying! Caveats: if you depend on plugins to give you an IDE-like experience in Vim, kak is not for you. Your vim plugins won't work. If you use Windows but don't want to use Cygwin, kak is not for you.
        • Tarean 9y ago
• RubenSandwich 9y ago
  Regardless if you feel like if the NeoVim refactor is worth it or not we can all agree that it is tremendous effort to modernize code written over the course of decades. Great job guys on another release!
  • agumonkey 9y ago
    The versionning repository should be a book about software engineering.
• fcanela 9y ago
  Major version can make someone think nvim is still unstable. My experience is the opposite. I have being using it for 2-4 years (can't remember exactly) and got the same 0 problems I run into Vim. Earlier versions required you to recompile NeoVim to enable new features for plugins. Yesterday I installed NeoVim in my new laptop and it was a smooth experience: Installed it using Ubuntu package manager, installed Vim-Plug for managing plugins, copied my old init.vim (or .vimrc), run vim and everything in order. I am really happy with NeoVim. I faced no problem with it that Vim could not resolve but I know the insides being a better ecosystem for core and plugins developers, so I will stick with it.
  • dkersten 9y ago
    Agreed. I've been using it for about 2 years without issue. I've also recently (within last 3 weeks) installed it on a fresh OS X install (on two, actually) and the experience was without incident and hassle free. The only thing that I had issues with was plugins using the remote api from node because I kept forgetting to install node_host (which was mentioned in the README and I just overlooked). Once I remembered to install that (and node locally), everything just worked.
  • dmos62 9y ago
    I tried jumping boat to nvim something like a year ago. One of my plugins ran into an issue, so I came back. A better question for us "old-vimers" is not "is nvim stable, because I'd like something modernized", but rather "what does nvim have that vim doesnt". I'm actually asking. My short glance led me to believe that it's got two things going for it: a) smoother interop with other "modern" tools b) cleaned up codebase. I'm using the word "modern" in a derogatory fashion to underline that we often mistake new for good.
    • ramy_d 9y ago
      I'm interested in neovim as well and I think you're asking a legitimate question. I would also add that if neovim is developer-friendly(er?) then that could also be a reason.
    • apazzolini 9y ago
• stewbrew 9y ago
  I understand why they started neovim, but don't think the split between vim 8 of today and neovim is a good thing. Makes me think of emacs vs xemacs but worth because they use slightly different dialects of vimscript (closures, currying in vim 8, different api for asynchronous calls). I personally wish they'd meet on some common, standardized ground. This would require both parties to accept they are not alone though. Edit: I realize that "Vim 8 features: partials, lambdas." might solve part of my problem.
  • godmodus 9y ago
    The diffwrence in performance is hhuuuugggee! Vim lags on my project, nvim doesnt! Quadcorei5, 16hb ram!
    • majewsky 9y ago
      What are you doing that makes Vim lag? In my experience (on much weaker hardware) it only lags noticeably when you do wildly unusual stuff, e.g. huge files or files with huge lines.
      • omaranto 9y ago
        On an old netbook (remember those?) Vim would lag just entering text in insert mode when I was editing LaTeX files (and​ only LaTeX files as far as I could tell). Slowness of LaTeX syntax highlighting is a known problem (the help files have a section called tex-slow). Trying all the suggestions there didn't speed things up enough for me. I tried editing without syntax highlighting for a while (this did work and completely solved the lag), but eventually just switched to Emacs.
      • godmodus 9y ago
        Editing latex(colors, parens, higjlighting, syntax check) Scala (700 lines/file) Managed to do more with nvim - yet to try syntactic again, thatll be the real test) but so far amuch more stable experience movement wise. (the files i work on are huge and im tasked with refactoring, so i cant avoid the hugeness)
    • 9y ago
• ptero 9y ago
  I have been using Vim as my primary editor for many years and am happy with it. People I know who use developer editors are split between Vim and Emacs. Neovim usage is minimal. Why? It is an honest question. I see developers of the editor happy, which is a good thing, but IMO to get more users NV must show why it is better from a user perspective -- have several demos on the powerful things easily achieved with NV that are painful with Vim (via plugins is OK). If NV devs can do this, it will go far. If not, then the case for an upgrade hasn't been made yet for most users. My 2c.
  • fao_ 9y ago
    Honestly for me the main reason was that it finally has builtin `:terminal`. The plugins for use with vim have always been slightly buggy for me.
    • 101km 9y ago
      Can you please elaborate how you make use of the built in terminal emulation of neovim? Whenever I see a mention I think "neat" but have yet to integrate it into my workflow.
      • has2k1 9y ago
        Not parent, but I use Neovim and Ranger [1] filemanager and I have a shortcut to open Ranger in a split or full window from which I can browse and open a file. You can do this only because Neovim has a built-in terminal. This may end up replacing vinegar [2] as my in-VIM filemanager. [1] https://github.com/ranger/ranger https://github.com/ranger/ranger [2] https://github.com/tpope/vim-vinegar https://github.com/tpope/vim-vinegar
        • cschneid 9y ago
          So the nesting you have is Shell -> Nvim -> Ranger, so ranger is contained inside of a vim split? Mind sharing some docs on how to do that?
• musaffa 9y ago
  I use Neovim on daily basis. It works really well. It requires tremendous efforts and love to transform a huge archaic code base into a much modern one. Thanks, Neovim team!
  • mundanevoice 9y ago
    This can be said for any rewrite. Let's wait and see what happens to Neovim's code in coming 10-15 years if it can last that long. When you have to support all the legacy systems and all types of OSes out there, crap is going to come in the code.
    • riffraff 9y ago
      To be fair, supporting all legacy systems and all types of OSes seems to be an explicit non-goal of neovim.
      • mundanevoice 9y ago
        Neovim does have breaking changes from Vim, that by definition make support for some of these systems very hard or impossible.
• garou 9y ago
  The efforts of Neovim team are well-intentioned and we are seeing it shaking the ViM development. (the previous major version from (7.0) 2006, before it (6.0) 2001). We love updates after all.
  • pekk 9y ago
    I wouldn't read too much into changes of version numbers. vim was being updated continuously.
    • garou 9y ago
      The versions numbers talk about the changes happening and compatibility. There's just a few new features in the 7.3 [1]: Persistent undo, More encryption, Conceal text, Lua interface, Python3 interface. [1] http://vimdoc.sourceforge.net/htmldoc/version7.html http://vimdoc.sourceforge.net/htmldoc/version7.html
• erikb 9y ago
  I'd say the info provided in the github releases is interesting, but it doesn't provide the necessary oversight a general info text would give. Can't really say what happened. Even if it was a stabilizing release it would be nice to see that somewhere.
• lunixbochs 9y ago
  This release fixes one of the biggest bugs with asynchronously embedding Neovim (some input states would just block the API), and makes ActualVim more reliable as a result. Neovim embedding works pretty well now, and will only get better. I'm hoping it will be possible soon to embed the entire Vim experience into another editor with little to no tradeoffs on either side. I've been impressed when interacting with the Neovim developers.
  • dmix 9y ago
    Neat, for those unfamiliar as I was: > Actual uses an embedded Neovim instance to accurately manipulate each Sublime Text buffer as though you were editing the text directly in vim, without breaking any Sublime Text features (aside from multiple selection for now). https://github.com/lunixbochs/actualvim https://github.com/lunixbochs/actualvim
    • lunixbochs 9y ago
      That needs amending: - It also breaks the automatic (while typing) completion and snippet suggestion popups (though Sublime's autocomplete has been wired into Vim and works great there) - Sublime's undo works but isn't coalesced properly while you're in Vim mode (but Vim's works fine there).
  • pmoriarty 9y ago
    I'd love to see neovim embedded in Firefox, and have it be just a standard part of every text field. Having a seperate editor window pop up as with the It's All Text extension is just not the same. It'd also be great if there was a way to have neovim "wrap" arbitrary shell commands, kind of like rlwrap[1] does, only with full vim editing features available instead of the relatively crippled readline. [1] - http://utopia.knoware.nl/~hlub/uck/rlwrap/ http://utopia.knoware.nl/~hlub/uck/rlwrap/
    • voidz 9y ago
      I wish something like this were available for Chrome. My Firefox use has been declining. Not really sure why. Though the termination of the addons language (xul?) in favor of webextensions is probably a big reason.
• hestefisk 9y ago
  Any reports on how stable the Windows release is?
  • seren 9y ago
    I don't know if it'an issue on my side, but I have not manage to do anything with the :terminal on Windows 7. It starts a prompt but I can not input anything in Terminal mode. I tried 'i' to go in insert mode in the terminal but it does not seem to work either. (To be sure this is not something in my vimrc, I tried with and without it). At that point I am not sure if this is a problem between chair and keyboard or a bug.
    • numeromancer 9y ago
      - Download and extract neovim win64 package - Start nvim-qt.exe - Get message box saying "The Neovim process has crashed" - Go back to Vim
      • uzantonomon 9y ago
        Same experience here.
• voidz 9y ago
  The only thing that bugs me about neovim is that it seems to require workarounds to get the escape button to behave the same as in vim. When I press escape to exit insert mode, there is a small delay. If I press a key (e.g. 'j' to go down) too quickly after Escape, it inserts the 'j' and cancels what escape is meant to do. In tmux I know of a workaround (iirc, 'set escape-delay 0' or something similar), but I wish I didn't have to change a tmux setting so one program can function. It's really annoying.. but ultimately worth it, I guess. That said — to the neovim team: congratulations ​on reaching the 2.0 milestone!
  • rofrol 9y ago
    Have tried the newest version? I couldn't reproduce this delay. And btw. it's version 0.2 not 2.0
• JdeBP 9y ago
  My first impression was not a good one. Its hardwired assumption of xterm control sequences, even when TERM says something else entirely, caused it to be unusable on my terminal (which understands DECSLPP as DECSLPP). * https://github.com/neovim/neovim/blob/v0.2.0/src/nvim/tui/tui.c#L423 https://github.com/neovim/neovim/blob/v0.2.0/src/nvim/tui/tu...
  • voidz 9y ago
    So, what terminal do you use?
    • JdeBP 9y ago
      I use several. But this particular one is most definitely not xterm, nor dtterm. Ironically, it actually implements both of DECSLPP and DECSCPP, but without the restrictions to only some sizes. So nvim could use these DEC VT control sequences to set the screen size. Unfortunately, there is no simple mechanism for nvim to know this. There's no terminal type that a user could set that would hint at this ability, let alone a termcap/terminfo capability. Nonetheless, just blithely assuming that every terminal type in existence implements dtterm's idiosyncratic extensions to the DEC VT control sequence set is wrong. There is a way for nvim to be told that the terminal is likely to have dtterm's idiosyncrasies, or indeed xterm's. nvim even uses it to detect other terminal types with other idiosyncratic control sequence extensions. It actually becomes usable once this bug is fixed. * https://github.com/jdebp/neovim/commit/3304de142b60efe8728c0b10183f820e9195d293 https://github.com/jdebp/neovim/commit/3304de142b60efe8728c0...