default run task

[tobdub-snce]

It would be nice if there was a default run task (build + execute), similar to the existing default build and test tasks.

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Run the default build task from launch configuration (#32239)
• Improve Configure Default Build task in multi root setup (#35312)
• Tasks -> Configure Default Build Task does not preserve comments (#37138)
• Suggest primary build task (#29444)
• Improve Run \[Build\] Tasks command and dialog (#47449)

[alexr00]

@tobdub, are you referring to the configurations in launch.json which run when you use F5 or click the green arrow in the debug viewlet?

[tobdub-snce]

@alexr00, I'm talking about tasks under Shift+Ctrl+P -> Tasks: Run task
There are default tasks for Build and Test. I'm looking for a default Run task i.e. build + execute.
F5 and Ctrl+F5 seem to require a debugger?

[Gama11]

There's a Debug: Start Without Debugging command that might be helpful? But I guess that only makes sense if the thing you want to start can be debugged, otherwise you wouldn't have a launch config for it.

[tobdub-snce]

The specific case I have at the moment is a Rust project where I want to trigger the cargo run task with a default keybinding in the same way I can trigger cargo build using the default build task.
I can create a keybinding for the specific task, but I thought it could make sense to have a default run task since it seems to be a fairly common operation, available in most editors/IDEs.

[alexr00]

@weinand do you think a feature request like this makes more sense as a type of task, or as a debugger-less launch.json configuration?

[weinand]

@alexr00 IMO this feature makes more sense as a task because typical projects already have some VS Code independent "run" script (or "run" makefile target) that they want to surface painlessly as a VS Code "Run" task (similar to "Build"). So there is no need to implement a "Run" task; it is only necessary to wire it up as a standard "Run" task.

The "Debug: Start Without Debugging" is very VS Code specific and requires an existing launch configuration (and a debugger extension that actually supports to launch a debug target without debugging). Since this is much more effort and the result is VS Code specific, most user are probably not interested in this.

[alexr00]

@weinand that sounds reasonable.

[xrob]

I believe this can be achieved with a change in the settings.json file similar to what I've done below:

"code-runner.executorMap": {
    "java": "mvn -B -q compile && java -cp ./target/classes com.something.$fileNameWithoutExt",
}