User configurable menus

We now allows extension writer to contribute menu items. The next logical step is to allow user to configure their menus - this is analog to the keybindings-story. One idea is to have a menus.json file which defines your menus:

{
  "editor/context": [
  {
    "command": "my command",
    "when": "editorHasSelection"
  },
  {
   // more..
  }
  ],
 "explorer/context": [
   // more ...
  ]
}

[manad777]

This feature would be really good.

Most plugin authors don’t use the context menu at all. They expect you to memorize their keyboard shortcuts, or bring up the command palette, search for a command, navigate to it, and press Enter.

It’s way better if you put the power in the hands of the user and let them create their own context menu entries for when plugin devs come up short. That way, you don’t need to remember anything, you right-click and select the command you want.

This especially helps for infrequently used plugins where you can’t remember the plugin name or the command name.

[mhwombat]

This feature is essential to me. I don’t want to have to memorise dozens of key bindings. Being able to customize key bindings isn’t enough; I work with too many languages, types of documents, etc. to remember key bindings for even common tasks.