Closed felixjung closed 7 years ago
OK, just to try what that would do, I deleted ultisnips. Performance is great now. Any recommendations how to fix ultisnips performance? Or should I just switch to a different snippet manager?
NCM get ultisnips candidates by sync API call, which is kind of heavyweight.
You don't need to delete ultisnips, though, use this to disable the built-in ultisnips source.
let g:cm_sources_override = {
\ 'cm-ultisnips': {'enable':0}
\ }
Future work (maybe):
g:cm_complete_delay
does not supress candidate calculation. Maybe we need to change the behavior, or add another config for this.Awesome! Thanks.
A new option g:cm_complete_start_delay
is added. Set it to non-zero value when you have to deal with slow, sync completion source.
see #119
Sweet. Thanks. Now that I know I can disable UltiSnips, I think I prefer having a quickly showing menu without ultisnips.
Hi,
First of, thanks for this great plugin! It's so much more straight forward compared to other solutions.
Unfortunately, I've noticed some quite bad performance problems in insert mode with NCM. Here's what this looks like when I'm pressing and holding the
DEL
key. I experience the frequent stops and delays when typing as well.I've tried increasing the
g:cm_complete_delay
setting. It seems to have helped somewhat, but not really. Settingg:cm_auto_popup
to0
mostly helps fixing these performance issues. But I get the feeling that some completion source is just really bad.Here's the output I get from profiling neovim:
Is ultisnips the problem here?
Thanks a lot! Would really love to keep using NCM!