You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you, it's reassuring to confirm that I'm not the only one who has encountered this issue recently. I was about to open a similar issue a few minutes ago but wasn't sure if I reproduced it correctly. I am also on Neovim nightly. For me the segmentation fault happens when typing '*./%.rc in a buffer (sometimes it does not crash immediately). When nvim-cmp is uninstalled the issue does not occur.
FAQ
Announcement
Minimal reproducible full config
Description
When I go into a c like file and start writing the comment
//1.
i get a segmentation faultI'm pretty sure it is the dot that is doing it.
I feel it is an issue with cmp-path in combination with another cmp source like buffer.
I use the lastest neovim from master 0.8-dev (commit: e6652821bd32e4ff8d62a0b67fc2041a5f41e252)
Do I need to make an issue in the main neovim repo. This seems serious.
Steps to reproduce
Go into any c like file and start wring
// 1.
and the issue should happen.With the config above of course.
Expected behavior
No segmentation fault.
Actual behavior
Segmentation fault
Additional context
No response
The text was updated successfully, but these errors were encountered: