-
Notifications
You must be signed in to change notification settings - Fork 27.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terminals launching using terminal.integrated.cwd do not check for invalid paths #17450
Comments
Is a variable a valid option to This would replace the need for @Tyriar's addin. |
@millergarym created #31677 |
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. It happens only if all 3 of these conditions are met:
More details:If I use the command When trying to toggle the terminal (without any currently opened): |
I have the same issue as #56849 , is there any solution to do this ? Split Terminal used to work, but now just trows |
I noticed this problem for the first time today. I get the same
|
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 I'm not sure why this only shows up with the "Split Terminal" command, though. |
@timdmackey the cwd in split terminal is driven by this: It sounds like inherited (likely) breaks when it contains a |
Invalid paths will cause the terminal to start at terminalProcess.js' dir.
The text was updated successfully, but these errors were encountered: