Clean up context menus

[daviddossett]

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:

• Folding large sections like Go to into their own submenu
• Moving Copy / Share / Copilot groups to the bottom so they are consistent across different menus

[emsaks]

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.

[generikvault]

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

[alfuken]

@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 -, it's a separator. As simple as that.). And later, maybe, allow editing this via a multistep command, or even a drag-n-drop GUI in a config editor.

WDYT?