The Run menu isn't related to running code in the runtime

[lionel-]

This is the first place I looked to get code-running functionality and inspect which options are available and which keybindings they are mapped to. But it only contains functionality related to the debugger.

• Should the Run menu be renamed to Debug to reduce the potential for confusion?

• Should we create a Console or Runtime menu which would collect all console/runtime related commands? This would be similar to the Terminal menu. Even if it only contains Execute line and Source file to begin with, it would be helpful to see at a glance what functionality is available and the default keybindings.

  Related to Add Run Line/Selection, Run Source command buttons to editor/context menus #754

[jmcphers]

See also https://github.com/posit-dev/positron-python/pull/181

[juliasilge]

Confusion around this spot in the activity bar came up in usability testing with @andrie today. Should this more clearly be about debugging code? Or should "Run and Debug" be a place to look for, say, how to run a Shiny app?

[jennybc]

I feel like this is an example of where the "general IDE" roots of VS Code are showing. It feels like it comes from a tradition where actually running or stepping through the code in front of your fingertips requires extra work, whereas to a large extent, the code our users care about can be immediately executed in the console with various gestures. I think it is interesting to think about what to do with menus like this that aren't relevant to Positron in the same way. I've got similar issues in the testing feature, e.g. with "Debug Tests".