8 ms·

Your blog post recommends using NeoVim today. I've considered looking at it several times, but the home page[1] still says Is it ready to download and run now

by eridius 11y ago

Your blog post recommends using NeoVim today. I've considered looking at it several times, but the home page[1] still says Is it ready to download and run now with all the features? No. Although some features are a work in progress, Neovim isn't at a stable point. Using Neovim should be done with caution as things may change. This warning is why I haven't yet tried switching over. Are they just being overly-cautious? [1]: http://neovim.io http://neovim.io

UberMouse 11y ago
I use Neovim as my daily editor, it definitely has it's quirks over Vim (sometimes it takes over 10 seconds to write to certain files, locking up Neovim and there are some bugs with the fuzzy finder I use that cause file corruption that aren't present in Vim) but on the whole it's pretty stable. Haven't encountered any issues yet that are more than a minor annoyance.
- jberryman 11y ago
  File corruption and sketchy saving sounds like a nightmare
- simoncion 11y ago
  > ...there are some bugs with the fuzzy finder I use that cause file corruption... Having your text editor corrupt the file it's working on sounds like the absolute worst case scenario. Is this fuzzy finder thing some third-party plugin? Do you have any idea why it corrupts the files that you point it at?
  - UberMouse 11y ago
    It's a third party plugin, it's definitely a Neovim issue because the file corruption doesn't happen with Vim. No idea why it happens. I'm fine living with it because I just check the file back out if it corrupts it. It's only an issue when opening a new file so it doesn't cause work to be lost. A github issue about it https://github.com/junegunn/fzf/issues/206 https://github.com/junegunn/fzf/issues/206
cgag 11y ago
I use it daily and it's been fine. I use it with true color support enabled, and a terminal that supports true color, and a patched version of tmux that supports true color, and finally all color schemes render as they do in gvim! Also the terminal emulator feature is awesome.
- TheSoftwareGuy 11y ago
  yeah, there is a good chance you'll not run into problems. however new, serious bug reports come in frequently. for example a lot of people have been seeing segfaults, and nobody seems to know where to look. Although Neovim's codebase is significantly cleaner than vim's, its still a far cry from what I would call good.
akurilin 11y ago
Been using it daily for several months now, haven't had much trouble with it. Worked seamlessly with over half a decade of accumulated vim plugins and config modifications.
uxcn 11y ago
I've been trying it for roughly the last month. I have run into a few quirks, for example it uses non-blocking i/o for things with libuv (for stdin), which can interfere with parent processes that expect blocking i/o. If you file a bug report, the issue usually gets fixed quickly. I've kept vim installed as a fallback so I can easily use vim if I run into anything that is a show-stopper, at least until it's fixed in nvim. I still plan on submitting patches to both for the foreseeable future though.
anon4 11y ago
Try kakoune[0]. As far as I can see, it's stable today. Just try not to think about how the name sounds shitty. [0] https://github.com/mawww/kakoune/ https://github.com/mawww/kakoune/
- eridius 11y ago
  But that's not Vim-compatible. I have a ton of Vim plugins that I rely on. Switching to a brand new editor is rather untenable.

by eridius 11y ago

UberMouse 11y ago

I use Neovim as my daily editor, it definitely has it's quirks over Vim (sometimes it takes over 10 seconds to write to certain files, locking up Neovim and there are some bugs with the fuzzy finder I use that cause file corruption that aren't present in Vim) but on the whole it's pretty stable. Haven't encountered any issues yet that are more than a minor annoyance.

jberryman 11y ago
File corruption and sketchy saving sounds like a nightmare
simoncion 11y ago
> ...there are some bugs with the fuzzy finder I use that cause file corruption... Having your text editor corrupt the file it's working on sounds like the absolute worst case scenario. Is this fuzzy finder thing some third-party plugin? Do you have any idea why it corrupts the files that you point it at?
- UberMouse 11y ago
  It's a third party plugin, it's definitely a Neovim issue because the file corruption doesn't happen with Vim. No idea why it happens. I'm fine living with it because I just check the file back out if it corrupts it. It's only an issue when opening a new file so it doesn't cause work to be lost. A github issue about it https://github.com/junegunn/fzf/issues/206 https://github.com/junegunn/fzf/issues/206

cgag 11y ago

I use it daily and it's been fine. I use it with true color support enabled, and a terminal that supports true color, and a patched version of tmux that supports true color, and finally all color schemes render as they do in gvim! Also the terminal emulator feature is awesome.

TheSoftwareGuy 11y ago
yeah, there is a good chance you'll not run into problems. however new, serious bug reports come in frequently. for example a lot of people have been seeing segfaults, and nobody seems to know where to look. Although Neovim's codebase is significantly cleaner than vim's, its still a far cry from what I would call good.

akurilin 11y ago

Been using it daily for several months now, haven't had much trouble with it. Worked seamlessly with over half a decade of accumulated vim plugins and config modifications.

uxcn 11y ago

I've been trying it for roughly the last month. I have run into a few quirks, for example it uses non-blocking i/o for things with libuv (for stdin), which can interfere with parent processes that expect blocking i/o. If you file a bug report, the issue usually gets fixed quickly. I've kept vim installed as a fallback so I can easily use vim if I run into anything that is a show-stopper, at least until it's fixed in nvim. I still plan on submitting patches to both for the foreseeable future though.

anon4 11y ago

Try kakoune[0]. As far as I can see, it's stable today. Just try not to think about how the name sounds shitty. [0] https://github.com/mawww/kakoune/ https://github.com/mawww/kakoune/

eridius 11y ago
But that's not Vim-compatible. I have a ton of Vim plugins that I rely on. Switching to a brand new editor is rather untenable.