Closed thekswenson closed 3 years ago
So you do have that problem if your terminal is big enough to show the call signatures?
What's your :set wrap?
"wrap" is set. In this case, the problem occurs even when the terminal is wide enough to show the call signature.
The problem does not occur when "nowrap" is set.
The problem has something to do with the number of characters in the line above the one I'm editing (the line that is written over with the call signature: if I delete the right number of characters from the line above, then the error will not occur. Also, if I resize the width of the terminal I can make wide enough so that the wrap doesn't occur.
Have you tried using the cmdline-window mode instead?
There might be a bug here for sure, but it seems none of the maintainers is eager to investigate, so also please feel free to do so yourself.. :)
Please try/test #652 and provide feedback there - it might help in your case. See https://help.github.com/articles/checking-out-pull-requests-locally/ for help on checking it out locally.
I've checkout out your pull request locally. It doesn't seem to alleviate the problem... I see identical behavior.
The issue is weird in general. Do you see it often?
Can you try it with a minimal vimrc, and/or bisect which other plugin might cause it?
Same issue as #493. We are trying to get rid of changing the buffer for this feature and are trying to use floating windows.
Issue
When adding a function call the pop-up call signature often needlessly wraps to span 2 lines. Here is an example:
Steps to reproduce
Versions
In case you are not using jedi-vim from Git master, please test it there, too.
Output of the "JediDebugInfo" command (in a Python buffer)
Output of the "messages" Vim command
Output of "scriptnames" Vim command