-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add support for text editor actions "go to next annotation" & "go to previous annotation" #248
Comments
I investigated a little. It turns out, since CDT LSP uses the CDT uses some kind of Job for updating the annotation model and available occurrences depending on the current selection ( Since the |
CDT-LSP has not implemented anything here (yet). I've to check what LSP4E can do for us. |
They work for breakpoints, markers, and the not-yet-merged spelling support. |
Hello @ghentschke, |
It seems that LSP4E already provides annotations: It seems that work has to be done in LSP4E here. Please check the @travkin79 it would be great if you provide a PR here! |
It should work when these keys are defined. The Include in next/previous navigation is enabled in the annotations preferences and it's possible to jump from occurrence to occurrence. |
@travkin79 Can you please open an issue for that in LSP4E. |
Thank you @ghentschke, I'll close this issue since the actual issue is in LSP4E. See eclipse-lsp4e/lsp4e#909 |
Not a CDT LSP issue. See eclipse-lsp4e/lsp4e#909 |
Editors like CDT's C++ editor and JDT's Java editor have support for the tool bar actions "next annotation" & "previous annotation" for navigating to the next / previous occurrence of a symbol / identifier (see action bar buttons).
![image](https://private-user-images.githubusercontent.com/10887297/302672130-4b400cc2-0b1a-48a4-abfa-0deb9d9599f8.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1NzM4MzYsIm5iZiI6MTczOTU3MzUzNiwicGF0aCI6Ii8xMDg4NzI5Ny8zMDI2NzIxMzAtNGI0MDBjYzItMGIxYS00OGE0LWFiZmEtMGRlYjlkOTU5OWY4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE0VDIyNTIxNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTU0NGI3NTI1ZjIwN2I2MzdjNjU5YWQ2OGQ0MjZmMzA4MTYzYzhhNjM2N2JhM2QzNzVlYTcxZGUwZTk2NGUxZTcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.V4qkIP7KtuBoYxIQqU1atYL_iz04T00hDImOuQjtK9s)
These buttons are also activated for the LSP-based C++ editor, but nothing happens if you push them. It would be great if that could be fixed.
The text was updated successfully, but these errors were encountered: