-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
Clean up context menus #225411
Comments
Maybe merge the Goto and Peek options - have a clickable 'peek' icon on the Goto entry to peek instead of opening new window. Also, the copy/paste/cut can be shrunk into one row of icons like in the Windows 11 Explorer context menu. |
Wouldn't it be nice if we could just pin and unpin commands from the command pallet to the context menu? Probalby similar to the keyboard shutcuts. Some extensions fill the context menu with entries that I basicly never use. There is already a feature request for custom menus: #9285 |
@generikvault is right. What you're suggesting @daviddossett is only cleaning up the mess of the items added by the vanilla VSCode, but the real problem is waaay beyond that. A more generic solution is long overdue. How about an ability for the user to create context menu "folders" at will, and then pin/unpin commands to either those folders or to context menu root directly? For starters via JSON config directly (I'd assume it'd be a plain tree, where if key is one of the existing commands - then it's a command, and if not - it's a folder. And if it's a dash WDYT? |
I made an extension that can partially make the contextmenu cleaner: https://github.com/BHznJNs/vscode-custom-contextmenu |
Context menus, especially in editors and notebooks, have grown substantially in size and variety as VS Code has evolved. There are inconsistencies to address (e.g. Share is in a different place in different menus) and organizational improvements that could be made.
Here's a rough sketch that looks at:
Go to
into their own submenuThe text was updated successfully, but these errors were encountered: