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.)
You can just try with reporting them as an issue on GitHub.. :)
Re:Neovim v0.4.0
by CameronNemo on Monday September 16, 2019 @11:36AM
(#20985102)
I use macOS and iTerm2, never experienced a crash. Perhaps one of your plugins is causing the issue?
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.