Skip to content
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

jedi-vim showing too many popups #531

Closed
strin opened this issue Jan 18, 2016 · 4 comments
Closed

jedi-vim showing too many popups #531

strin opened this issue Jan 18, 2016 · 4 comments

Comments

@strin
Copy link

strin commented Jan 18, 2016

screen shot 2016-01-18 at 12 05 54 pm

My .vimrc only has

syntax on                           " syntax highlighing
filetype on                          " try to detect filetypes
filetype plugin indent on    " enable loading indent file for filetype
set rtp+=~/.vim/bundle/vundle/
call vundle#rc()

" jedi-vim: awesome Python autocompletion.
Plugin 'davidhalter/jedi-vim'

@blueyed
Copy link
Collaborator

blueyed commented Jan 18, 2016

Confirmed.

Seems to be a Jedi issue though.. signatures at

signatures = get_script().call_signatures()
is [<CallSignature: abspath index 0>, <CallSignature: abspath index 0>, <Ca llSignature: abspath index 0>, <CallSignature: abspath index 0>, <CallSignature: abs path index 0>].

blueyed added a commit to blueyed/jedi-vim that referenced this issue Jan 18, 2016
Jedi might return multiple call signatures, where the string
representation is the same.  This patch filters out duplicates.

Fixes davidhalter#531.
@blueyed
Copy link
Collaborator

blueyed commented Jan 18, 2016

See #532 for a quick attempt to fix this - although I'm not sure this should be handled in jedi-vim - probably not.

@blueyed
Copy link
Collaborator

blueyed commented Jan 8, 2017

FWIW, getting only 3 (same) signatures currently.

@davidhalter
Copy link
Owner

Fixed since probably Jedi 0.15.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants