rox

I'll work on this after https://github.com/ncm2/ncm2/issues/67 . This is also related to https://github.com/ncm2/ncm2/issues/18 It should be done after snippet interface stabilization I'm still short of time, there's no ETA.

Cannot reproduce. You could try a different version of jedi library.

The memory issue is probably related to older python's memory leak. https://www.python.org/dev/peps/pep-0442/ It is hard to reproduce and I haven't come across this issue for a long tmie. Let's wait...

hmm... I'm ok with thoes lines, they don't break anything yet.

I think it's fine to keep them.

Now we have a case: https://github.com/ncm2/ncm2-jedi/issues/10

I'm not sure what you what. After the snippet is expanded, ultisnips will automatically jumps to the first snippet tabstop/placeholder. If you're encountering wired behavior, better to post a gif...

If you want a different order of placeholder, you should modify the snippet instead of modify the plugin

You could wrap your own `forward_or_cr` key so that you could map a key like this: `inoremap ncm2_ultisnips#expand_or("\forward_or_cr", 'm')`

I have exported two API, you should be able to program you own key mapping based on `ncm2_ultisnips#completed_is_snippet()` and `ncm2_ultisnips#inject_completed_snippet()`