-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
'Peek Definition' missing from context menu #85218
Comments
We have done that on purpose in an effort to cleanup the context menu. All peek-commands are still there, e.g accessible via keybindings or via the command palette but we redesign the context menu like this... Two options that I see
Personally, I'd prefer option 2 because it will keep the context menu small and gives all the power, however at the cost of being harder to discover. |
For completeness - this has been mentioned before here: #83752 (comment) |
How about grouping them all on a "Peek" submenu? That'd make them discoverable to folk who rely on right-click to find out what they can do on things (as opposed to reading the doc). |
Maybe this case can get some activity underway on #9827 🙏 |
Yeah, it would require to implement sub menus. I'll do some exploring |
I like this. Just wondering why the sequence of "Peek" options differs from the sequence of "Go to" options. |
The order should now be the same... Anyways, we aren't sold on the sub menu approach yet. There are concerns about this being too noisy and therefore some questions why you have missed "Peek Definition".
|
We will stick with the sub context menu for now. |
Issue Type: Bug
VS Code version: Code - Insiders 1.41.0-insider (bd8425f, 2019-11-20T09:17:36.311Z)
OS version: Windows_NT x64 10.0.17763
The keyboard equivalent (Alt+F12 on Windows) does still work.
On 1.40.1 it is there:
The text was updated successfully, but these errors were encountered: