forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Jedi: Peek Definition highlights till the last but one character in Python file #11535
Labels
area-intellisense
LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc.
bug
Issue identified by VS Code Team member as probable bug
Comments
tormec
added
triage-needed
Needs assignment to the proper sub-team
bug
Issue identified by VS Code Team member as probable bug
labels
May 1, 2020
Please inform if you're using Jedi or Language server, i.e check the value of |
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I can reproduce the bug, thanks! |
karrtikr
added
needs PR
area-intellisense
LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc.
and removed
info-needed
Issue requires more information from poster
triage
labels
May 4, 2020
Transferring this to Jedi davidhalter/jedi#1568 |
ghost
removed
the
needs PR
label
May 4, 2020
karrtikr
changed the title
Peek Definition highlights till the last but one character in Python file
Jedi: Peek Definition highlights till the last but one character in Python file
May 4, 2020
Closing in favour of #11995. |
ghost
removed
the
needs PR
label
Mar 16, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area-intellisense
LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc.
bug
Issue identified by VS Code Team member as probable bug
Same issue #5750
This is a screenshot with an example of code affected:
Extensions (3)
The text was updated successfully, but these errors were encountered: