Skip to content
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

Command line argument (--startingDirectory,-d) does not accept folders with spaces #4728

Closed
jasondicker-zz opened this issue Feb 26, 2020 · 6 comments
Labels
Area-Commandline wt.exe's commandline arguments Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@jasondicker-zz
Copy link

jasondicker-zz commented Feb 26, 2020

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.657]
Windows Terminal version: 0.9.433.0

Steps to reproduce

From the command line, run: wt -d c:\Users\Folder With Spaces

--or--

From the command line, run: wt -d "c:\Users\Folder With Spaces"

Expected behavior

Windows Terminal should open at the specified starting directory i.e "c:\Users\Folder With Spaces"

Actual behavior

Windows Terminal opens with the following error(s):

[error 0x80070002 when launching `With Spaces']

--or--

[error 0x8007010b when launching `cmd.exe']

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 26, 2020
@zadjii-msft
Copy link
Member

This will almost certainly get better with #4724.

This might be a duplicate of #4571

@zadjii-msft zadjii-msft added Area-Commandline wt.exe's commandline arguments Product-Terminal The new Windows Terminal. labels Feb 26, 2020
@german-one
Copy link
Contributor

@jasondicker Can you confirm that
wt -d "C:\Program Files"
works, while
wt -d "C:\Program Files\"
does not?

@jasondicker-zz
Copy link
Author

jasondicker-zz commented Feb 27, 2020

I can confirm that the trailing "\" causes the problem.

@german-one
Copy link
Contributor

Thank you for testing again! In that case it's a dup of #4571 and fortunately we have a potential fix already.

@zadjii-msft
Copy link
Member

Thanks for confirming!

/dup #4571

@ghost
Copy link

ghost commented Feb 27, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Feb 27, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 27, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Commandline wt.exe's commandline arguments Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants