-
-
Notifications
You must be signed in to change notification settings - Fork 370
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
Change default for show_call_signatures to 2 #412
Conversation
This appears to be less error-prone.
Hmm true, I'm just not sure if it's what I want. I actually like the way of Since we don't have the same opinion about this, I would like to gather community votes. If a majority of people prefers |
+1, even though less pretty. |
👎, because I like them also more (having tried the one in the command line for a while now). |
heh, there should be a meme for this situation. |
I'm closing this one now, doesn't seem to have generated a lot of interest. |
I vote |
Lol. Hell no. :) |
Why not? That's how docstring preview works. I guess that extending this feature for signatures is not a crazy idea. |
It would just add additional complexity. I already don't like specifying The docstring preview already support call signatures. They are added there. |
Well, I don't find that Perhaps I took the issue the bad way. Since the signature is in the docstring preview, a good alternative could be to delay the closing of the popup until the closing parenthesis:
This makes sense because the docstring can still be usefull while typing the parameters, too. |
This appears to be less error-prone.
E.g. with things like indenting plugins (Vimjas/vim-python-pep8-indent#41).