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
Argument list is shown in the docstring area #5577
Comments
Please inform if you're using Language server or Jedi, i.e check the value of If you see no such settings or if setting is In that case try adding |
I understand my report was mostly a dup of this, but anyway I was also pointing out the ill-formatting of the text in general, for example, above:
This can't just be attributed to the fixed size of the tooltip box, AFAICS. I understand reflowing the text is not that easy but surely there are better heuristics. And maybe the font of the docstring may be smaller. |
In this case, It's because of the docstring of the function, not because of any ill-formatting of text in vscode.
There's a line break after "input", which gets reflected in the intellisense as it should, not a bug. Please comment if you disagree, and I encourage you to file new issues if you see any possible enhancements. |
I perfectly understand that. My point was that some kind of reflowing of the text should be done, and the current heuristic (do nothing at all) is way too simplistic. |
If you can show other places where such cases are handled, we'll be happy to look into it. |
Both emacs and vim are quite good reformatting chunks of text and comments, see for example http://vimdoc.sourceforge.net/htmldoc/change.html#fo-table. In vscode you have Rewrap https://marketplace.visualstudio.com/items?itemName=stkb.rewrap, which seems to support markdown. I'm not saying this is an easy affair, but the screenshots here and in my report show that current formatting makes text rather unintelligible, so a best-effort approach, even with its own shortcomings, could improve things. Moreover, decreasing text size could help. |
Can you please open up a new issue just for this? If it bothers enough users, we can definitely look into such shortcomings and make a decision on whether we need it. |
I also believe current formatting in your earlier report is distorted just because of this #5577 bug (and it won't be that unintelligible once that's out of the way). This line break issue is the only one I see for now. Regardless, thanks for the suggestions. |
Ok, let's see, hopefully you're right and fixing this will considerably improve the situation. |
|
@karrtikr Which is rather useless but looks better. |
BTW, when you tag issues upstream-jedi are you actually reporting the problem upstream? |
Closing as this is an upstream issue which we don't have direct control or influence over. |
Environment data
Expected behaviour
Show all args.
Actual behaviour
Full arg list is not shown in the correct area and disappear when typing.
Steps to reproduce:
import torch
torch.nn.Conv2d(
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
; turn on source maps to make any tracebacks be useful by runningEnable source map support for extension debugging
)The text was updated successfully, but these errors were encountered: