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
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
importnumpyasnpnp.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:
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
letg:jedi#popup_on_dot=0
in that machine's rc-file.
The text was updated successfully, but these errors were encountered:
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.
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)
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:
Also notice that there is no function-argument completion.
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
in that machine's rc-file.
The text was updated successfully, but these errors were encountered: