Key scheme Microsoft Visual Studio does not apply on Open Declaration

[ghentschke]

The call hierarchy is great!! BUT, it's a real pain to navigate and has some issues. Arrow keys don't work.

You mean this behavior (tested under windows 11): https://github.com/user-attachments/assets/2d712902-6c14-44f7-9216-f9f26f942ac6

Yes, that behavior is desired. However, I might have multiple call sites for a function, as well as it may be several function calls deep. The focus is lost almost immediately, and then arrow keys are no longer operable until I again click into the call hierarchy pane.

A little confused by short-cut keys. Previously had "Open Declaration" bound to F12.

In Eclipse CDT? AFAIK the Eclipse default is F3. I know F12 is the default in VS Code.

Yes, I use the "Microsoft Visual Studio" key bindings Scheme in the "General->Keys" preferences area. See below for more details

however, pressing F3 (which should theoretically behave the same as clicking the context menu) actually takes me to the enclosing function, and not the one my cursor is on.

Hm, I cannot reproduce that. Can you place a small code snippet to illustrate this behavior?

It turns out I have "F3" bound to "Find Next" as is the default behavior for Microsoft Visual Studio key bindings, and it so happens that I had previously searched for the text initialize() so that when I pressed F3 it would search and find that text, which happened to be the enclosing function. So the real issue is that I can't seem to get the "Open Declaration" function bound to F12 through any means. I attempted to change all possible instances of "Open Declaration" to use F12 in the Windows->Preferences->General->Keys area, but in no case could I get it to work. The right-click context menu always shows F3 as the key binding, and F12 never works.

Originally posted by @kevin071586 in #461

[kevin071586]

Is there any way to hack around this issue in the near-term? Some configuration file somewhere that I can edit? I'm trying to force myself to use the new editor and it's great in most ways... but keybindings are one of those quality of life things that make a big difference when you're staring at the same editor 10 hours a day.

[ghentschke]

but keybindings are one of those quality of life things that make a big difference when you're staring at the same editor 10 hours a day.

I agree. I hope to find the time in the next week.

[ghentschke]

As a workaround you can change the key by changing the Open Hyperlink key:

This is because the CDT-LSP editor uses the generic text editor and technically it's an hyperlink in the editor we use to jump to the declaration/definition.

[kevin071586]

Fantastic, thank you. I did confirm setting the Open Hyperlink option to F12 works exactly as I'd expect for open declaration.

[ghentschke]

Did you tried the latest cdt-lsp build?

[kevin071586]

Did you tried the latest cdt-lsp build?

I think so, but I'm not confident I am pulling in any updates. I have the software set to install from "CDT-LSP - https://download.eclipse.org/tools/cdt/releases/cdt-lsp-latest" but I can't tell that my attempts to update are working. I probably need to fully remove CTD-LSP that came with 2025-R6 and attempt a re-install. Right now if I restore default bindings the hyperlink goes back to F3.

Installation details show:
C/C++ LSP Support Version 3.1.0.202504091618 (Provider: Eclipse CDT)

[ghentschke]

You need to update to the latest main branch build using this update page

[ghentschke]

Via Help -> Install New Software...
Add the page above as new update site:

[kevin071586]

Thanks, adding the main branch did work and I was able to get the updated 3.2.0.202505060924 version. (I could see the date embedded in the previous version I had and assumed I didn't have the most updated branch).

Indeed this version fixes the "Open Declaration" key binding and adds a context "When: C/C++ Editor (LSP)" that is by default bound to F12 for Microsoft Visual Studio scheme.

Thanks!