Cmder: VSCode tasks don't run properly on Cmder

Created on 13 Dec 2018  ·  25Comments  ·  Source: cmderdev/cmder

I've followed the instructions here and I'm able to run Cmder as VSCode integrated terminal.
Everything seems to be working fine, except for VSCode > Run Task which ouputs a lot of stuff but doesn't run the task.

Example:
VSCode > Terminal > Run Task > npm start

Integrated terminals shows:

Executing task: npm start
DEBUG(init.bat): Env Var - CMDER_ROOT=D:\Portables\cmder

DEBUG(init.bat): Env Var - debug-output=1

DEBUG(init.bat): Looking for Git install root...

DEBUG(:read_version): Env Var - git_executable=D:\Portables\cmder\vendor\git-for-windows\cmd\git.exe

DEBUG(:read_version): D:\Portables\cmder\vendor\git-for-windows\cmd\git.exe does not exist.

DEBUG(:validate_version): Found Git Version for VENDORED: ...

DEBUG(:read_version): Env Var - git_executable=C:\Program Files\Git\cmd\git.exe

DEBUG(:read_version): Env Var - GIT_VERSION_USER=2.18.0.windows.1

DEBUG(:validate_version): Found Git Version for USER: ...

DEBUG(:enhance_path): Env Var - find_query=C:\\Program\ Files\\Git\\cmd

DEBUG(:enhance_path): Env Var 1 - found=0

DEBUG(:enhance_path): Env Var 2 - found=1

DEBUG(:enhance_path): Env Var - find_query=C:\\Program\ Files\\Git\\mingw64

DEBUG(:enhance_path): Env Var 1 - found=0

DEBUG(:enhance_path): Env Var 2 - found=0

DEBUG(:enhance_path): BEFORE Env Var - PATH=C:\ProgramData\DockerDesktop\version-bin;C:\Program Files\Docker\Docker\Resources\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Git\cmd;C:\ProgramData\chocolatey\bin;C:\Users\epari\AppData\Roaming\nvm;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Yarn\bin\;C:\Users\epari\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\epari\AppData\Local\Microsoft\WindowsApps;C:\Users\epari\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\epari\AppData\Local\hyper\app-2.0.0\resources\bin;C:\Users\epari\AppData\Local\now-cli;D:\Path;C:\Users\epari\.dotnet\tools;C:\Program Files\dotnet;C:\Users\epari\AppData\Roaming\npm;C:\Users\epari\AppData\Local\Yarn\bin

DEBUG(:enhance_path): Appending 'C:\Program Files\Git\mingw64'

DEBUG(:enhance_path): AFTER Env Var - PATH=C:\ProgramData\DockerDesktop\version-bin;C:\Program Files\Docker\Docker\Resources\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Git\cmd;C:\ProgramData\chocolatey\bin;C:\Users\epari\AppData\Roaming\nvm;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Yarn\bin\;C:\Users\epari\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\epari\AppData\Local\Microsoft\WindowsApps;C:\Users\epari\AppData\Local\Programs\Microsoft
VS Code\bin;C:\Users\epari\AppData\Local\hyper\app-2.0.0\resources\bin;C:\Users\epari\AppData\Local\now-cli;D:\Path;C:\Users\epari\.dotnet\tools;C:\Program Files\dotnet;C:\Users\epari\AppData\Roaming\npm;C:\Users\epari\AppData\Local\Yarn\bin;C:\Program Files\Git\mingw64

DEBUG(:enhance_path): Env Var - find_query=C:\\Program\ Files\\Git\\usr\\bin

DEBUG(:enhance_path): Env Var 1 - found=0

DEBUG(:enhance_path): Env Var 2 - found=0

DEBUG(:enhance_path): BEFORE Env Var - PATH=C:\ProgramData\DockerDesktop\version-bin;C:\Program Files\Docker\Docker\Resources\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Git\cmd;C:\ProgramData\chocolatey\bin;C:\Users\epari\AppData\Roaming\nvm;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Yarn\bin\;C:\Users\epari\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\epari\AppData\Local\Microsoft\WindowsApps;C:\Users\epari\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\epari\AppData\Local\hyper\app-2.0.0\resources\bin;C:\Users\epari\AppData\Local\now-cli;D:\Path;C:\Users\epari\.dotnet\tools;C:\Program Files\dotnet;C:\Users\epari\AppData\Roaming\npm;C:\Users\epari\AppData\Local\Yarn\bin;C:\Program Files\Git\mingw64

DEBUG(:enhance_path): Appending 'C:\Program Files\Git\usr\bin'

DEBUG(:enhance_path): AFTER Env Var - PATH=C:\ProgramData\DockerDesktop\version-bin;C:\Program Files\Docker\Docker\Resources\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Git\cmd;C:\ProgramData\chocolatey\bin;C:\Users\epari\AppData\Roaming\nvm;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Yarn\bin\;C:\Users\epari\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\epari\AppData\Local\Microsoft\WindowsApps;C:\Users\epari\AppData\Local\Programs\Microsoft
VS Code\bin;C:\Users\epari\AppData\Local\hyper\app-2.0.0\resources\bin;C:\Users\epari\AppData\Local\now-cli;D:\Path;C:\Users\epari\.dotnet\tools;C:\Program Files\dotnet;C:\Users\epari\AppData\Roaming\npm;C:\Users\epari\AppData\Local\Yarn\bin;C:\Program Files\Git\mingw64;C:\Program Files\Git\usr\bin

DEBUG(init.bat): Env Var - GIT_INSTALL_ROOT=C:\Program Files\Git

DEBUG(init.bat): Found Git in: 'C:\Program Files\Git'

DEBUG(:enhance_path_recursive): Env Var - add_path=D:\Portables\cmder\bin

DEBUG(:enhance_path_recursive): Env Var - position=

DEBUG(:enhance_path_recursive): Env Var - max_depth=1

DEBUG(:enhance_path_recursive): Adding parent directory - 'D:\Portables\cmder\bin'

DEBUG(:enhance_path): Env Var - find_query=D:\\Portables\\cmder\\bin

DEBUG(:enhance_path): Env Var 1 - found=0

DEBUG(:enhance_path): Env Var 2 - found=0

DEBUG(:enhance_path): BEFORE Env Var - PATH=C:\ProgramData\DockerDesktop\version-bin;C:\Program Files\Docker\Docker\Resources\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Git\cmd;C:\ProgramData\chocolatey\bin;C:\Users\epari\AppData\Roaming\nvm;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Yarn\bin\;C:\Users\epari\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\epari\AppData\Local\Microsoft\WindowsApps;C:\Users\epari\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\epari\AppData\Local\hyper\app-2.0.0\resources\bin;C:\Users\epari\AppData\Local\now-cli;D:\Path;C:\Users\epari\.dotnet\tools;C:\Program Files\dotnet;C:\Users\epari\AppData\Roaming\npm;C:\Users\epari\AppData\Local\Yarn\bin;C:\Program Files\Git\mingw64;C:\Program Files\Git\usr\bin

DEBUG(:enhance_path): Prepending 'D:\Portables\cmder\bin'

DEBUG(:enhance_path): AFTER Env Var - PATH=D:\Portables\cmder\bin;C:\ProgramData\DockerDesktop\version-bin;C:\Program Files\Docker\Docker\Resources\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Git\cmd;C:\ProgramData\chocolatey\bin;C:\Users\epari\AppData\Roaming\nvm;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Yarn\bin\;C:\Users\epari\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\epari\AppData\Local\Microsoft\WindowsApps;C:\Users\epari\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\epari\AppData\Local\hyper\app-2.0.0\resources\bin;C:\Users\epari\AppData\Local\now-cli;D:\Path;C:\Users\epari\.dotnet\tools;C:\Program Files\dotnet;C:\Users\epari\AppData\Roaming\npm;C:\Users\epari\AppData\Local\Yarn\bin;C:\Program Files\Git\mingw64;C:\Program Files\Git\usr\bin

DEBUG(:enhance_path): Env Var - find_query=D:\\Portables\\cmder

DEBUG(:enhance_path): Env Var 1 - found=0

DEBUG(:enhance_path): Env Var 2 - found=0

DEBUG(:enhance_path): BEFORE Env Var - PATH=D:\Portables\cmder\bin;C:\ProgramData\DockerDesktop\version-bin;C:\Program Files\Docker\Docker\Resources\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Git\cmd;C:\ProgramData\chocolatey\bin;C:\Users\epari\AppData\Roaming\nvm;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Yarn\bin\;C:\Users\epari\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\epari\AppData\Local\Microsoft\WindowsApps;C:\Users\epari\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\epari\AppData\Local\hyper\app-2.0.0\resources\bin;C:\Users\epari\AppData\Local\now-cli;D:\Path;C:\Users\epari\.dotnet\tools;C:\Program Files\dotnet;C:\Users\epari\AppData\Roaming\npm;C:\Users\epari\AppData\Local\Yarn\bin;C:\Program Files\Git\mingw64;C:\Program Files\Git\usr\bin

DEBUG(:enhance_path): Appending 'D:\Portables\cmder'

DEBUG(:enhance_path): AFTER Env Var - PATH=D:\Portables\cmder\bin;C:\ProgramData\DockerDesktop\version-bin;C:\Program Files\Docker\Docker\Resources\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Git\cmd;C:\ProgramData\chocolatey\bin;C:\Users\epari\AppData\Roaming\nvm;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Yarn\bin\;C:\Users\epari\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\epari\AppData\Local\Microsoft\WindowsApps;C:\Users\epari\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\epari\AppData\Local\hyper\app-2.0.0\resources\bin;C:\Users\epari\AppData\Local\now-cli;D:\Path;C:\Users\epari\.dotnet\tools;C:\Program Files\dotnet;C:\Users\epari\AppData\Roaming\npm;C:\Users\epari\AppData\Local\Yarn\bin;C:\Program Files\Git\mingw64;C:\Program Files\Git\usr\bin;D:\Portables\cmder

DEBUG(init.bat): Env Var - HOME=C:\Users\epari

Not sure if a bug in VSCode, cmder or in the integration between the two.

Upstream VSCode
Source
picture empz
👍5

Most helpful comment

https://github.com/cmderdev/cmder/pull/2113

picture SupinePandora43 on 25 Jun 2019
👍6

All 25 comments

@eparizzi what you are seeing is cmder debug output normally enabled using the init.bat /d command. What command is being run in vscode config?

daxgames picture daxgames on 13 Dec 2018
👍2

My VS Code integrated settings are:

"terminal.integrated.shell.windows": "C:\\Windows\\System32\\cmd.exe",
"terminal.integrated.shellArgs.windows": [
  "/k",
  "%CMDER_ROOT%\\vendor\\init.bat"
],

%CMDER_ROOT% points to D:\Portables\cmder where cmder is located.

The terminal works fine by using it normally. It just doesn't work when running a VS Code task.

empz picture empz on 13 Dec 2018

I meet the same problem.
When I run the build task, it will run perfect.
image
but when I run the "run task", the terminal shows:
image

my tasks.json:

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "Build",
      "command": "g++",
      "args": [
        "-g",
        "-Wall",
        "-fexec-charset=GBK",
        "-std=c++17",
        "-lm",
        "${file}",
        "-o",
        "${fileDirname}/${fileBasenameNoExtension}.exe"
      ],
      "problemMatcher": {
        "owner": "cpp",
        "fileLocation": "absolute",
        "pattern": {
          "regexp": "^(.*):(\\d+):(\\d+):\\s+(error):\\s+(.*)$",
          "file": 1,
          "line": 2,
          "column": 3,
          "severity": 4,
          "message": 5
        }
      },
      "group": {
        "kind": "build",
        "isDefault": true
      }
    },
    {
      "label": "Run",
      "type": "shell",
      "dependsOn": "Build",
      "command": "${fileDirname}/${fileBasenameNoExtension}.exe",
      "args": [],
      "presentation": {
        "echo": true,
        "reveal": "always",
        "focus": false
      },
      "problemMatcher": [],
      "group": {
        "kind": "test",
        "isDefault": true
      }
    }
  ]
}

and my VSCode integrated settings are the same as @eparizzi .
I had set the %CMDER_ROOT% .

lengthmin picture lengthmin on 1 Jan 2019
👍2

i have encountered the same problem. wondering if it has been solved?
not only so many DEBUG(....) messages are output, it seems like the command in tasks.json does not actually run at all

hyc0612 picture hyc0612 on 1 Mar 2019

Vscode is feeding in an argument that init.bat is seeing as a '/d' See the references PR fir a workaroind

daxgames picture daxgames on 1 Mar 2019

BTW, the reason for this issue has been explained by @patstew here:
https://github.com/Microsoft/vscode/issues/48986#issuecomment-389588952

The problem is that the VS Code documentation recommends doing this to start cmder:

"terminal.integrated.shell.windows": "C:\\WINDOWS\\System32\\cmd.exe",
"terminal.integrated.shellArgs.windows": ["/K", "C:\\cmder\\vscode.bat"]

and you can only have one /K or /C, so appending another one to do the task doesn't work. You'd need to to end up with an arguments array like:
["/K", "C:\\cmder\\vscode.bat", "&", "task_command", "task_arg"]

DRSDavidSoft picture DRSDavidSoft on 9 Mar 2019

First of all, thank you for referring me the post.

but sorry, the answer from patstew is quite hard to understand for me.
("The problem is ?.... vscode documentation recommends?", ps. i am not a
native english speaker.)

Moreover, I can not understand the solution, too. "end up an arguments
array like ["/K", "C:\cmder\vscode.bat", "&", "task_command", "task_arg"]".
Does it mean arguments in my tasks.json? In my case, my command in
tasks.json is a python. then, the args would be args for python, it should
be wrong.

I can understand what caused this problem, "OK. Now I see. This is
currently not possible since a tasks already passes a command to the
cmd.exe. It would require that we add special code for cmder.exe that
injects the vscode.bat into the command when executing." from dbaeumer. (
https://github.com/Microsoft/vscode/issues/48986#issuecomment-390165000)

Thank you again.

David Refoua notifications@github.com 于2019年3月9日周六 下午8:54写道：

BTW, the reason for this issue has been explained by @patstew
https://github.com/patstew here:
Microsoft/vscode#48986 (comment)
https://github.com/Microsoft/vscode/issues/48986#issuecomment-389588952

The problem is that the VS Code documentation recommends doing this to
start cmder:

"terminal.integrated.shell.windows": "C:\WINDOWS\System32\cmd.exe","terminal.integrated.shellArgs.windows": ["/K", "C:\cmder\vscode.bat"]

and you can only have one /K or /C, so appending another one to do the
task doesn't work. You'd need to to end up with an arguments array like:
["/K", "C:\cmder\vscode.bat", "&", "task_command", "task_arg"]

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cmderdev/cmder/issues/1985#issuecomment-471174562,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AnBRq1kpuSPgEHG9P4OMwU5bMOO3GRZRks5vU68EgaJpZM4ZQ7kx
.

hyc0612 picture hyc0612 on 11 Mar 2019

@hyc0612 Sorry if my comment was unclear.

Basically, this means that a fix should be made to VS Code in order to make tasks work.

Unfortunately, there is no solution that you can use right now to make it work; instead the creators of VS Code and us should work on something to fix the problem.

Please wait while we work on either a fix or a workaround for this issue. 😉

DRSDavidSoft picture DRSDavidSoft on 11 Mar 2019

I had the same issues with cmder, couldn't get any of the supposed workarounds to actually work, finally got shark (a fork of cmder), it seems to be running fine. The config needed is the following:

"terminal.integrated.shellArgs.windows": [
    "/k C:\\shark\\modules\\init.cmd"
]
kamenminkov picture kamenminkov on 11 Mar 2019

@kamenminkov are you launching a shell using shark or are you running a task via vscode using shark? Shell should work the same with shark and cmder. Tasks should fail in both based on Microsoft/vscode#48986 (comment)). The failure on shark though should be different than what is reported here. Instead of all the debug messages reported by cmder users the task would just not run at all.

daxgames picture daxgames on 11 Mar 2019

@daxgames Sorry, my bad, ignore my previous comment; I was not launching tasks through the native VSCode feature but by using Quick Task. Shark and cmder differ (for me at least) only by that cmder outputs all that debug info before showing the prompt (shark shows the prompt right away); both shark and cmder seem to break the task the moment the prompt is initialised. I suppose it's a matter of how (in what order) the arguments are passed to cmd.exe.

kamenminkov picture kamenminkov on 18 Mar 2019

@kamenminkov you are experiencing exactly as I thought but explained poorly

daxgames picture daxgames on 18 Mar 2019

There is a hacky way to get tasks to work. As by default using the Cmder shell with tasks will fail. However, in the associated tasks.json file, we can override the VSCode shell and default behaviour for tasks, and have Cmder initialized a bit more manually:

{
    "version": "2.0.0",
    "windows": {
        "options": {
            "shell": {
                "executable": "cmd.exe",
                "args": [
                    "/d", "/c", "[cmder_root]\\vendor\\init.bat", "&&"
                ]
            }
        }
    },
    "tasks": [
        {
            "label": "Build",
            "type": "shell",
            "command": "cd ${workspaceFolder}/build && make"
        },
...

This, when placed in the tasks.json file will override the shell specifically to run said tasks, without the need to modify the regular VSCode settings.json.

StableCoder picture StableCoder on 19 Mar 2019
🎉1

@StableCoder This works if I disable the "terminal.integrated.shellArgs.windows" setting, which defeats the whole purpose - if I want to open a new terminal without a task, it opens a bare cmd. I wouldn't mind bare cmd for tasks themselves.

kamenminkov picture kamenminkov on 21 Mar 2019
👍1

I could not make it work.
@kamenminkov and @StableCoder
Did it work for you?

My option was to create a script in bash and put the git-bash that comes in the cmder as the default terminal. I had to run rsync.

kayzzen01 picture kayzzen01 on 19 Apr 2019

I could not make it work.
@kamenminkov and @StableCoder
Did it work for you?

Yes. I just re-tested in 1.33.1, and it works fine. This is my whole tasks.json file I used to use Cmder specifically as the task shell, since using it without spews plenty of garbage:

{
    // See https://go.microsoft.com/fwlink/?LinkId=733558
    // for the documentation about the tasks.json format
    "version": "2.0.0",
    "windows": {
        "options": {
            "shell": {
                "executable": "cmd.exe",
                "args": [
                    "/d", "/c", "C:\\tools\\Cmder\\vendor\\init.bat", "&&"
                ]
            }
        }
    },
    "tasks": [
        {
            "label": "BuildIt",
            "type": "shell",
            "command": "cd ${workspaceFolder}/build && make && echo All done!",
            "group": {
                "kind": "build",
                "isDefault": true
            }
        }
    ]
}

Again, specifying it in the tasks.json file overrides just the task shell environment. Shouldn't affect regular integrated terminal use, or the specified "terminal.integrated.shellArgs.windows" in the regular settings.json file.

StableCoder picture StableCoder on 19 Apr 2019
👍3

What works for me is just specifying cmd.exe in tasks.json (I don't want to be polluting project-wide tasks with stuff specific to me) and passing the tasks as shell commands (as opposed to using the type property for things like gulp and npm). So at the top I have just that:

{
    "version": "2.0.0",
    "windows": {
        "options": {
            "shell": {
                "executable": "cmd.exe",
                "args": ["/d", "/c"]
            }
        }
    },
    // ...
}

... and instead of using the type property for things like npm and gulp, I pass them on directly to the shell, i.e. instead of

{
    // ...
    "tasks": [
        {
            "type": "npm",
            "script": "start",
            "problemMatcher": [
                "$gulp-tsc"
            ],
            // ...
        }
    ]
}

I have

{
    // ...
    "tasks": [
        {
            "label": "default",
            "command": "npm run start",
            "type": "shell",
            "args": [],
            "problemMatcher": [
                "$gulp-tsc"
            ],
            "presentation": {
                "group": "dev",
                "reveal": "always",
                "focus": false,
                "panel": "dedicated"
            },
            "group": "build",
            "runOptions": {
                "runOn": "folderOpen"
            }
        }
    ]
}

This even works to start tasks at project open. What doesn't always work is interrupting the task with Ctrl+C (thus I have to kill the whole terminal instance), but it might be a different, unrelated bug.

kamenminkov picture kamenminkov on 22 Apr 2019
👍6

@StableCoder and @kamenminkov

Thank you ! I'll take your example and test.

kayzzen01 picture kayzzen01 on 29 Apr 2019

https://github.com/cmderdev/cmder/pull/2113

SupinePandora43 picture SupinePandora43 on 25 Jun 2019
👍6

2113

Got the vscode_init.cmd file mentioned in the above PR and moved it to my %CMDER_ROOT%/vendor/bin and updated my setting.json as shown by @SupinePandora43

Cmder now runs tasks normally without any issues for me

ajaymittur28 picture ajaymittur28 on 10 Jul 2019

@ajaymittur28 , i created vscode_init script specially for fixing vscode tasks!

SupinePandora43 picture SupinePandora43 on 10 Jul 2019
❤4

would this work even if the shell for vs code is set to powershell, together with cmder ?
or does this only work for cmd.exe?

a4z picture a4z on 7 Oct 2019

@a4z , its uses cmd.exe for starting vscode_init.cmd, if it has arguments -> run these commands (using cmd.exe), if it has no arguments -> run vendor\init.bat

SupinePandora43 picture SupinePandora43 on 7 Oct 2019

I experienced the same problem. I am forced to remove the cmder integration from vscode to do debugging

erlangp picture erlangp on 8 Dec 2019

I experienced the same problem. I am forced to remove the cmder integration from vscode to do debugging

already have a solution

2113

lengthmin picture lengthmin on 8 Dec 2019
Was this page helpful?
0 / 5 - 0 ratings

Related issues

AaronKaa picture AaronKaa  ·  3Comments
spooky picture spooky  ·  3Comments
bmeverett picture bmeverett  ·  3Comments
justinmchase picture justinmchase  ·  3Comments
tfarina picture tfarina  ·  3Comments