Change:
conptyInheritCursor: true }; <del> stat(shellLaunchConfig.executable!).then(stat => { </del> <ins> const cwdVerification = stat(cwd).then(async stat => { if (!stat.isDirectory()) { return Promise.reject(SHELL_CWD_INVALID_EXIT_CODE); } }, async err => { if (err && err.code === 'ENOENT') { // So we can include in the error message the specified CWD shellLaunchConfig.cwd = cwd; return Promise.reject(SHELL_CWD_INVALID_EXIT_CODE); } }); const exectuableVerification = stat(shellLaunchConfig.executable!).then(async stat => { </ins> if (!stat.isFile() && !stat.isSymbolicLink()) { <del> return this._launchFailed(stat.isDirectory() ? SHELL_PATH_DIRECTORY_EXIT_CODE : SHELL_PATH_INVALID_EXIT_CODE); </del> <ins> return Promise.reject(stat.isDirectory() ? SHELL_PATH_DIRECTORY_EXIT_CODE : SHELL_PATH_INVALID_EXIT_CODE); </ins> } <del> this.setupPtyProcess(shellLaunchConfig, options); </del> }, async (err) => { if (err && err.code === 'ENOENT') { let cwd = shellLaunchConfig.cwd instanceof URI ? shellLaunchConfig.cwd.path : shellLaunchConfig.cwd!; const executable = await findExecutable(shellLaunchConfig.executable!, cwd); if (!executable) { <del> return this._launchFailed(SHELL_PATH_INVALID_EXIT_CODE); </del> <ins> return Promise.reject(SHELL_PATH_INVALID_EXIT_CODE); </ins> } } <ins> }); Promise.all([cwdVerification, exectuableVerification]).then(() => { </ins> this.setupPtyProcess(shellLaunchConfig, options); <ins> }).catch((exitCode: number) => { return this._launchFailed(exitCode); </ins> }); }

Discussion:
Invalid paths will cause the terminal to start at ' dir.
Is a variable a valid option to ? If so what variables? eg the directory of the current active document. This would replace the need for addin.
created
Would you suggest me to work on this thing and
Sorry for the delay, anything with the help wanted label is up for grabs
I'm sorry if it's not the correct issue to post this. I came here from following a bunch of now closed issues. So in case it could help you figure out what's wrong with this: I am having the very same error as described by . It started just after I upgraded budgie 17.10 (based on ubuntu) to 18.04 It happens only if all 3 of these conditions are met: have no terminal opened in the current instance of vscode. have several folders opened in the workspace have no specified (more on this below). If I use the command instead of the command , it prompts me to chose one of the opened folders in the workspace, and the terminal always starts successfully in this case. When trying to toggle the terminal (without any currently opened): The terminal fails to start with: set to either or . But the terminal starts successfully with a static value such as .
I have the same issue as , is there any solution to do this ? Split Terminal used to work, but now just trows 'chdir(2) failed' and 'The terminal process command '/bin/bash -l' failed to launch (exit code: 1)'
I noticed this problem for the first time today. I get the same error when I try to split the terminal. The issue occurs whenever I use the "Split Terminal" command. Using the "New Terminal" command does not throw this error.
After investigating a little further, the problem in my case is being caused by a unicode character in my file path. One of the folders in my file path is , and the apostrophe (right single quote) is the root of the problem. Removing that character from the folder name fixes it. I'm not sure why this only shows up with the "Split Terminal" command, though.
the cwd in split terminal is driven by this: ! It sounds like inherited (likely) breaks when it contains a ? Can you create a new issue for this?