-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update runtime version to 18.08 #20
Conversation
I'm afraid that something in my Vim configuration still causes this to segfault as soon as I enter insert mode. (If I move my
It's caused by "ultisnips" and looks suspiciously similar to SirVer/ultisnips#1032. |
It seems utilsnips upstream issue. I don't know what we can do about it. You may try running it through Sdk to catch more useful backtrace. |
As discussed at #20 (comment) this seems to prevent UltiSnips from causing a segfault. Very mysterious.
I disagree: if a Vim extension can cause Vim to crash, this is a Vim bug. And the same version of Ultisnips does not cause eg Fedora 29's Vim to crash, even though it is also linked against Python 3.7. So it is evidently possible to compile a Vim which doesn't crash when running this extension. I compared what's different between Fedora's and this Vim's |
Perfect! I assume we're good to go with this PR then? |
Thanks for the nudge to try to track this down! |
No description provided.