The shell commands can only run inside a shell such as DIR for cmd and if for bash. So when you want to run shell commands, you have to use “type”: “shell” setting to run it correctly. When you want to just run a program such as .bat, .sh or .exe, then you can just … Read more
Here is something that will work. Basically you make another task in which you include all the other tasks that you want to run on your preLaunchTask with the dependsOn keyword. Code for reference: “tasks”: [ { “label”: “CleanUp_Client”, “type”: “shell”, “command”: “rm”, “args”: [ “-f”, “Client” ] }, { “label”: “Client_Build”, “type”: “shell”, “command”: … Read more
Not a perfect solution, but I found a workaround to create a keybinding that can be activated at a workspace level. In the workspace .vscode/settings.json file, set a new setting to true. (Because the setting is not registered by vscode or any extension, it will be displayed faded out in the editor – This is … Read more
The problem is that “Run Test Task” and “Run Build Task” do not execute all tasks in that specific group. Usually you get a drop down selection so you can choose which task to execute. Since you have specified one of the tasks as default, the selection will be skipped and instead the default task … Read more
On Linux systems you should use: “terminal.integrated.shellArgs.linux” On Windows and OSX: terminal.integrated.shellArgs.windows and terminal.integrated.shellArgs.osx respectively. If you want to apply shellArgs setting on a per-workspace basis – you can, despite the fact that documentation says: The first time you open a workspace which defines any of these settings, VS Code will warn you and subsequently … Read more
You can always use bash as your task runner and then assign arbitrary terminal commands as your tasks. { “version”: “0.1.0”, “command”: “bash”, “isShellCommand”: true, “showOutput”: “always”, “args”: [ “-c” ], “tasks”: [ { “taskName”: “My First Command”, “suppressTaskName”: true, “isBuildCommand”: true, “args”: [“echo cmd1”] }, { “taskName”: “My Command Requiring .bash_profile”, “suppressTaskName”: true, “args”: … Read more
If you want to completely delete settings, go to %UserFolder%\AppData\Roaming\Code and delete the whole folder. Then uninstall and install it again. If you want to delete all extensions too, delete the extensions folder on %UserFolder%\.vscode.
November 2018 Update As of this commit (and a few subsequent follow-ups), you can now add a clear presentation option to your task to have it clear the terminal before each task run. Working example (on fresh clone+build): { // See https://go.microsoft.com/fwlink/?LinkId=733558 // for the documentation about the tasks.json format “version”: “2.0.0”, “tasks”: [ { … Read more
This worked for me. Note all these are required, even though none are important: problemMatcher.pattern.regexp problemMatcher.pattern.file problemMatcher.pattern.location problemMatcher.pattern.message problemMatcher.background.activeOnStart problemMatcher.background.beginsPattern problemMatcher.background.endsPattern { // See https://go.microsoft.com/fwlink/?LinkId=733558 // for the documentation about the tasks.json format “version”: “2.0.0”, “tasks”: [ { “label”: “build-extras”, “type”: “shell”, “isBackground”: true, “command”: “./script/build-extras”, // This task is run before some debug tasks. … Read more
It needs to be setup so that Code is found in your PATH. If you’re on a mac system, do the following (for windows systems, read below): Launch VS Code Open up command palette (press F1) and type shell command to find Shell Command: Install ‘code’ command in PATH command. Restart terminal If you’re on … Read more