-
-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature request] Async call signature fetching #761
Comments
I don't know how easy asynchronous stuff is with Jedi. what do you think @blueyed? It's probably only possible with neovim and VIM 8+? right? I don't think Python's threading would be enough. |
Not sure either. We should maybe consider to hook into the existing vim-echodoc framework? |
I think #652 addresses this. |
Just noticed that #420 is also from me, but older - it might be obsolete, or only some parts would be still relevant. |
@morphheus |
My biggest pet peeve with call signatures is the initial delay required for loading the module containing the desired function. This delay is fairly short, ~500ms on average, maybe 1s for Scipy stuff. However, it blocks visual updates, preventing the user from seeing what they type until the call signature can be displayed.
Ideally, the module loading should be done in asynchronously.
This is something I would be willing to implement myself. How much work would be required for such a change? I'm also not sure how this would tie in with the open PR #420 .
The text was updated successfully, but these errors were encountered: