Initial debug configurations

Describe the bug I had trouble setting up the extension, because

1. I expected the extension to come with a basic debug configuration, but
2. I did not see it - I had to add one to launch.json myself.

I found this, so you are probably aware of automatic debug configurations: https://github.com/ManuelHentschel/VSCode-R-Debugger/blob/4fd0e703860a53cffbbc9fe2d086bd949098a078/src/extension.ts#L25 (Update: I guess I was wrong here: you’re not using DebugConfigurationProviderTriggerKind.Dynamic nor onDebugDynamicConfigurations anywhere.)

But as I said, I don’t see them. This is after I click “Show all automatic debug configurations”:

What works is pressing F5 - then, I get this:

but then this:

and this:

So then I opened C:\Temp. Debug configurations are still empty.

Then, upon F5, I get this: (Which is weird because C:\Program Files\R\R-4.0.2\bin\R.exe is exactly the path my R binary.)

Still, clicking “Open launch.json”, it opens a launch.json with three entries pre-filled (Launch Workspace, Debug R-File, Debug R-Function). And now I also see them in the launch panel, and debugging works without changing any path.

In summary:

• One needs to open a folder workspace for debugging to work.
• Something is weird with the R path before the debug config is added
• Automatic debug configs do not seem to work(?). Compare https://code.visualstudio.com/updates/v1_45#_automatic-debug-configurations https://code.visualstudio.com/updates/v1_45#_providing-debug-configurations-dynamically

[ManuelHentschel]

I had expected automatic debug configurations to be listed immediately, but this does not seem to be the case when you don’t have any other configuration, even after opening a .R file. This experience is still suboptimal, but that’s how it works in VS Code apparently.

This is probably intentional, since listing all automatic debug configurations would require activating all installed debugger extensions, which might take some time

[ManuelHentschel]

I forgot to say that I don’t seem to be setting this variable anywhere. R.exe is in my %PATH%, so it’s probably found there. We might branch this off into a separate issue 😉

I just added automatic quotes if the path contains spaces and an option to add custom command line arguments for the call to R. Thah should hopefully work for everyone.