"Debug using launch.json" confusing experience when a launch.json exists #146
Description
Testing #141
Here I had an existing launch.json with no configs for python. I see those configs, the dynamic configs from Python, and the option to add a config. From the command name, I think I am expecting to add a launch.json config, or pick an existing Python config? But I see stuff that is unrelated to Python or launch.json.
If this is the experience you want, I think that's fine, it's just a shortcut to the "select and start debugging" command, but I wouldn't say it's "using launch.json". And also if so, maybe it makes the different in experience confusing between the cases where I have a launch.json and where I don't.