6 ms·

> Otherwise it is pretty much a drop-in replacement without issues. Except for the crashes. The crashes are an issue. Don't get me wrong though, I like nvim.

by mths 7y ago

> Otherwise it is pretty much a drop-in replacement without issues. Except for the crashes. The crashes are an issue. Don't get me wrong though, I like nvim. I use it occasionally. But the crashes are an issue.

tadzik_ 7y ago
Interesting. Are you using some sophisticated plugins, some unusual platform? I've aliased vim to neovim a few years ago and it has not crashed once for me.
- mths 7y ago
  OSX. Plugins: ale, bufexplorer, nerdtree, rust.vim, vim-airline, vim-airline-themes, vim-colors-solarized I generally start vim in my src folder on Monday and exit it on Friday. Occasionally, just on a whim, I run nvim instead. Mostly its fine. But the times I've experienced crashes or other hickups like rendering bugs forcing me to :qa!, it's been on nvim. Edit: Oh and I run it in the terminal, iTerm2 to be precise.
  - afarrell 7y ago
    I wonder if any 2-4 of the folks who’ve never had it crash would find it fun to join in a mob-debugging session where you screenshare, we all open an discord* channel, and we try and figure out the cause and solution. —— (* IM could be discord, gitter, slack, or whatever. I’d argue strongly against IRC because I think the lack of support for code blocks and especially newlines makes it harder to talk about code/stacktraces.)
    - blueyed 7y ago
      You can just try with reporting them as an issue on GitHub.. :)
  - CameronNemo 7y ago
    I use macOS and iTerm2, never experienced a crash. Perhaps one of your plugins is causing the issue?
the_duke 7y ago
After using nvim for several years, I've never seen it crash once.
- wyclif 7y ago
  Same here. I use it constantly with a handful of plugins, never had an issue.
deleted 7y ago
[deleted]
AdamGibbins 7y ago
I've been using neovim for years now, I've never once had a crash.
seanhunter 7y ago
No crashes here and I use it all day pretty much every day. They only real negative in my view is the startup time which is noticeably worse than vim for me. Advantages I see are - unix clipboard and middle mouse pasteboard both work out of the box without having to recompile (ie "*p and "+p and the corresponding yanks just work) whereas on vim for whatever reason I always have to rebuild my distro vim and faff about with terminals for ages - the substitution preview thing above is really great - the "terminal" window type which I don't use much but a lot of people do - the fact you have native support for python3 and python2 plugins simultaneously. Don't even want to think about how many goats had to be sacrificed to build that feature but it's cool - the ":checkhealth" diagnostic screen that gives you useful info to allow you to easily fix any problems you're having with terminal and plugin setup
- blueyed 7y ago
  > They only real negative in my view is the startup time which is noticeably worse than vim for me. Check that this is not e.g. due to Python host detection/setup - you might have plugins that trigger both py2/py3 hosts to load for example. (hosts can be configured explicitly to skip it) Also check `nvim --startuptime /tmp/nvimlog`.

by mths 7y ago

tadzik_ 7y ago

Interesting. Are you using some sophisticated plugins, some unusual platform? I've aliased vim to neovim a few years ago and it has not crashed once for me.

mths 7y ago
OSX. Plugins: ale, bufexplorer, nerdtree, rust.vim, vim-airline, vim-airline-themes, vim-colors-solarized I generally start vim in my src folder on Monday and exit it on Friday. Occasionally, just on a whim, I run nvim instead. Mostly its fine. But the times I've experienced crashes or other hickups like rendering bugs forcing me to :qa!, it's been on nvim. Edit: Oh and I run it in the terminal, iTerm2 to be precise.
- afarrell 7y ago
  I wonder if any 2-4 of the folks who’ve never had it crash would find it fun to join in a mob-debugging session where you screenshare, we all open an discord* channel, and we try and figure out the cause and solution. —— (* IM could be discord, gitter, slack, or whatever. I’d argue strongly against IRC because I think the lack of support for code blocks and especially newlines makes it harder to talk about code/stacktraces.)
  - blueyed 7y ago
    You can just try with reporting them as an issue on GitHub.. :)
- CameronNemo 7y ago
  I use macOS and iTerm2, never experienced a crash. Perhaps one of your plugins is causing the issue?

the_duke 7y ago

After using nvim for several years, I've never seen it crash once.

wyclif 7y ago
Same here. I use it constantly with a handful of plugins, never had an issue.

deleted 7y ago

[deleted]

AdamGibbins 7y ago

I've been using neovim for years now, I've never once had a crash.

seanhunter 7y ago

No crashes here and I use it all day pretty much every day. They only real negative in my view is the startup time which is noticeably worse than vim for me. Advantages I see are - unix clipboard and middle mouse pasteboard both work out of the box without having to recompile (ie "*p and "+p and the corresponding yanks just work) whereas on vim for whatever reason I always have to rebuild my distro vim and faff about with terminals for ages - the substitution preview thing above is really great - the "terminal" window type which I don't use much but a lot of people do - the fact you have native support for python3 and python2 plugins simultaneously. Don't even want to think about how many goats had to be sacrificed to build that feature but it's cool - the ":checkhealth" diagnostic screen that gives you useful info to allow you to easily fix any problems you're having with terminal and plugin setup

blueyed 7y ago
> They only real negative in my view is the startup time which is noticeably worse than vim for me. Check that this is not e.g. due to Python host detection/setup - you might have plugins that trigger both py2/py3 hosts to load for example. (hosts can be configured explicitly to skip it) Also check `nvim --startuptime /tmp/nvimlog`.