-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Ycm GotoDeclaration/Definition causes vim to freeze in certain cases #3458
Comments
YouCompleteMe: fa92f40 |
Also, using |
I've noticed this recently too. I'm looking into it. |
Found the culprit. |
Until we figure out how to fix this, use |
bstaletic
added a commit
to bstaletic/ycmd
that referenced
this issue
Oct 19, 2019
PR ycm-core#1275 broke GoTo in python in more ways than one. See: - ycm-core/YouCompleteMe#3458 - ycm-core#1341 Changes in the behaviour: - GoTo, GoToDefinition and GoToDeclaration now do what GoToType used to do. - We don't expose jedi's `goto_assignments` which can be useful, but we do have GoToReferences that calls jedi's `usages()`. - This means that `GoTo` on `self.x` will now jump to the definition of the type of `x`, while `GoToReferences` will do what is expected. - The `goto_usages` for this case returns "weird" locations, see ycm-core#1341 for details.
bstaletic
added a commit
to bstaletic/ycmd
that referenced
this issue
Oct 19, 2019
PR ycm-core#1275 broke GoTo in python in more ways than one. See: - ycm-core/YouCompleteMe#3458 - ycm-core#1341 Changes in the behaviour: - GoTo, GoToDefinition and GoToDeclaration now do what GoToType used to do. - We don't expose jedi's `goto_assignments` which can be useful, but we do have GoToReferences that calls jedi's `usages()`. - This means that `GoTo` on `self.x` will now jump to the definition of the type of `x`, while `GoToReferences` will do what is expected. - The `goto_usages` for this case returns "weird" locations, see ycm-core#1341 for details.
Fixed. |
@bstaletic Cool! Appreciate the good work! |
ObiWahn
pushed a commit
to ObiWahn/ycmd
that referenced
this issue
Dec 2, 2019
PR ycm-core#1275 broke GoTo in python in more ways than one. See: - ycm-core/YouCompleteMe#3458 - ycm-core#1341 Changes in the behaviour: - GoTo, GoToDefinition and GoToDeclaration now do what GoToType used to do. - We don't expose jedi's `goto_assignments` which can be useful, but we do have GoToReferences that calls jedi's `usages()`. - This means that `GoTo` on `self.x` will now jump to the definition of the type of `x`, while `GoToReferences` will do what is expected. - The `goto_usages` for this case returns "weird" locations, see ycm-core#1341 for details.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Prelude
Please complete these steps and check these boxes (by putting an
x
insidethe brackets) before filing your issue:
[Frequently Asked Questions][faq] section.
about to report and couldn't find an answer to my problem. ([Example Google
search.][search])
vim --version
.:YcmDebugInfo
.the
:YcmToggleLogs
command.version) I am using.
my issue, including what I expected to happen and what actually happened.
that any help I receive is a selfless, heartfelt gift of their free time. I
know I am not entitled to anything and will be polite and courteous.
actually perform all of these steps.
Thank you for adhering to this process! It ensures your issue is resolved
quickly and that neither your nor our time is needlessly wasted.
Issue Details
All the completion works fine tho, both identifier and semantic.
when invoking
GoToDeclaration
orGoToDefinition
on thesomevalue
property, vim freezes.jump to the
__init__
function, or at least not freeze.Diagnostic data
Output of
vim --version
Output of
YcmDebugInfo
Contents of YCM, ycmd and completion engine logfiles
ycm_015czata.log
ycmd_51139_stderr_iqtdumfz.log
OS version, distribution, etc.
I have tested on Linux and MacOS. Same behavior
The text was updated successfully, but these errors were encountered: