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

(vim <7.3) function-argument completion may insert text into buffer #13

Closed
obreitwi opened this issue Oct 17, 2012 · 2 comments
Closed

Comments

@obreitwi
Copy link

When using jedi-vim with vim versions prior to 7.3 (I tested with 7.2), the function-argument completion may sometimes inject text into the actual buffer.

Steps to reproduce:

  • Start vim 7.2 to edit a new python file.
  • Type the following
import numpy as np
np.linspace( 1, 2, 3 )

Also notice that there is no function-argument completion.

  • Place your cursor behind the 3 and press "." in insert mode. The buffer will then look like the following:
import num≡jedi=0, py as np≡ (start, stop, *num=50*, endpoint=True, retstep=False) ≡jedi≡
np.linspace( 1, 2, 3. )

The text is inserted into the buffer and will be written to disk with the next save.
My guess would be that it has something to do with the missing "conceal" feature, but I've had no time to investigate further. For the time being I simply set

    let g:jedi#popup_on_dot=0

in that machine's rc-file.

@davidhalter
Copy link
Owner

Thank you for the detailed error report. I instantly knew what was wrong.

This: let g:jedi#popup_on_dot=0 would not completely solve the issue (just FYI). Pull again. And please test it once again on that machine, without that setting.

@obreitwi
Copy link
Author

I can confirm that the bug is gone now, ty.

On Wed, Oct 17, 2012 at 11:32:55AM -0700, David Halter wrote:

Thank you for the detailed error report. I instantly knew what was wrong.

This: let g:jedi#popup_on_dot=0 would not completely solve the issue (just FYI). Pull again. And please test it once again on that machine, without that setting.


Reply to this email directly or view it on GitHub:
#13 (comment)

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

No branches or pull requests

2 participants