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
Today I cloned the package pynvim and installed the package directly instead from PyPi.
After reopening nvim I noticed that nvim was very laggy in all python files.
I found out that the issue was with Ultisnips.
Deleting the package and reinstalling it from PyPi made the lag go away.
The version of pynvim on PyPi is 4.3 and so I went through the git history to check where something significant changed.
I located the issue to be this PR neovim/pynvim#506.
This PR changes a num_to_str function to include a boolean check.
The helper function is used in the LegacyVim object's eval function here.
Browsing through this repo's source code reveals that Ultisnips uses vim.eval at many places.
I wonder what could be done to circument this issue?
Profiling different variations of the num_to_str function did not reveal any significant speed up 🤠
I have also made an issue at pynvim's repo here.
The text was updated successfully, but these errors were encountered:
@jsr-p That sucks... yet another new bug that only affects neovim. I am sorry, but I cannot support neovim currently.
This issue was closed due to it only affecting Neovim and not core Vim.
Why is Neovim only best-effort?
UltiSnips maintenance is a lot of work. Reproducing bug reports is tedious, slow and error prone. The current maintainers have to limit their scope to provide a reasonable level of service to the community.
Neovim should work with any plugin that core vim works with. But in the past, Neovim support has been difficult for UltiSnips: It regularly had bugs that did not affect the core Vim distributions, i.e. Vim, gVim, MacVim, and Vim for Windows and its testing approach required a completely separate code path from core as well. Therefore, currently Neovim bugs are considered on a best effort basis.
UltiSnips is looking for an additional maintainer that is interested in bringing the Neovim level of service on par with core Vim. If you are interested in helping out, please reach out to SirVer.
Hi
Today I cloned the package pynvim and installed the package directly instead from PyPi.
After reopening nvim I noticed that nvim was very laggy in all python files.
I found out that the issue was with
Ultisnips
.Deleting the package and reinstalling it from PyPi made the lag go away.
The version of pynvim on PyPi is 4.3 and so I went through the git history to check where something significant changed.
I located the issue to be this PR neovim/pynvim#506.
This PR changes a
num_to_str
function to include a boolean check.The helper function is used in the LegacyVim object's
eval
function here.Browsing through this repo's source code reveals that
Ultisnips
usesvim.eval
at many places.I wonder what could be done to circument this issue?
Profiling different variations of the
num_to_str
function did not reveal any significant speed up 🤠I have also made an issue at
pynvim
's repo here.The text was updated successfully, but these errors were encountered: