-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
deoplete-jedi does show proper module completions on import statements like "from x.y" #191
Comments
Reproduced. But it is hard to fix for me. @blueyed Ping. Can you fix the problem? |
@Shougo, thank you very much for your help! By the way, looks like [RFC] Update Jedi PR fixes this issue - I've tried to reproduce this fix by myself and issue with broken completions disappeared. Hope this will help. |
OK. I have merged it. |
@Shougo , could you please reopen this issue? Looks like it still persists after update. However, I was able to overcome this by updating |
@zabulazza
Please elaborate.. this PR is merged, i.e. |
So maybe you only have to run |
@blueyed, excuse me for confusing you - my previous statement was unclear. Ok, so basically I had following situation - I have only reproduced fix for Please, let me know in case if I can help you somehow or if I need provide you an additional information , because I am really interested in this plugin working. |
@zabulazza I am not using deoplete/deoplete-jedi by default myself currently, but rather jedi-vim and only enable deoplete manually.. it is too much overhead and subtle bugs for me. My last WIP for deoplete-jedi was to use Jedi more directly (#184), but I think it needs the caching still (because deoplete is calling it so often). I suggest:
|
OK. Reopened. |
#184 fixes it. |
Problem summary
Deoplete-jedi shows list of all modules on completions like 'from x.y'. Please see example.
Expected
Deoplete-jedi shows completion only for proper modules
Environment Information
Provide a minimal init.vim with less than 50 lines (required)
Generate logfiles if appropriate
Then look at and attach the files
/tmp/nvim-log_{PID}
and/tmp/deoplete.log
here.Steps to reproduce the issue after starting Neovim (required)
Screen shot (if possible)
Provided in summary
Upload the logfile(s)
https://pastebin.com/yQAT9VX2 - deoplete log
The text was updated successfully, but these errors were encountered: