-
Notifications
You must be signed in to change notification settings - Fork 38
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
When using clangd, clicking on items in "references" panel (alt+shift+f12) doesn't jump to line #27
Comments
Sorry I never got back to this but this should be fixed in 0.19.2! |
Doesn't work on 0.19.3 with either clangd or rust-analyzer. |
Ope I'm a moron. This is the references sidebar. Will push an update with the fix soon since I messed this up. |
I found that if I have a full-file editor and subset editors, if I focus the full-file editor and use Ctrl-G to jump to a line, sometimes Haystack will jump to another editor of a sub-block other than the one I have focused. Is this related? |
I do not think that is related to this bug, but I will fix that as well! |
This should finally be fixed in 0.19.4! |
Does this issue occur when all extensions are disabled?: (references view unavailable without clangd)
Haystack Version: 0.19 (I installed 0.19.1 AUR but apparently it self-reports as 0.19.0?)
VS Code Version: 1.90.0
Chromium: 122.0.6261.156
OS: {3 }
Steps to Reproduce:
Haystack opens the relevant file or focuses a code editor of the correct file (or a function-local editor of the correct or incorrect function), but does not jump to a line. If I right-click a result, click Copy, then Ctrl+G and paste the description (beginning with a line and character), then it jumps to the correct location.
This does not occur on stock VS Code with similar settings (jumps to line correctly).
The text was updated successfully, but these errors were encountered: