Using neovim, one is able to use not only python2 or python3 but both. When doing so, clang_complete will default to python2 whereas ultisnip will default to python3, causing jumping between parameters to break.
Ultisnip provides a variable (UltiSnipsUsePythonVersion) to alter this behavior, setting the used python-version to the same value in both plugins fixes the issue.
Maybe introducing such a variable to clang_complete or defaulting to python3 altogether would be a good idea.
Using neovim, one is able to use not only python2 or python3 but both. When doing so, clang_complete will default to python2 whereas ultisnip will default to python3, causing jumping between parameters to break.
Ultisnip provides a variable (UltiSnipsUsePythonVersion) to alter this behavior, setting the used python-version to the same value in both plugins fixes the issue.
Maybe introducing such a variable to clang_complete or defaulting to python3 altogether would be a good idea.