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.

Sign up for GitHub

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

Jump to bottom

wt.exe should start powershell/cmd in CURRENT folder #9445

Closed
alex-jitbit opened this issue Mar 11, 2021 · 4 comments
Closed

wt.exe should start powershell/cmd in CURRENT folder #9445

alex-jitbit opened this issue Mar 11, 2021 · 4 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@alex-jitbit
Copy link

Steps to reproduce

Type wt.exe in command prompt, windows commander, or anywhere else

Expected behavior

Windows Terminal should launch in the CURRENT FOLDER. That is how command line works. Look at git - when you type it in - it starts working in the current folder.

Actual behavior

It always launches in %user% folder
@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 Mar 11, 2021
@zadjii-msft
Copy link
Member

This is by-design - the terminal is obeying your startingDirectory setting. If you launch wt.exe -d . it will inherit the CWD of the caller. wt -d c:\windows\system32 and it'll launch in c:\windows\system32. #3547, #878 (comment) and #878 (comment) have more details.

/dup #878

@ghost
Copy link

ghost commented Mar 11, 2021

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 Mar 11, 2021
@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 Mar 11, 2021
@alex-jitbit
Copy link
Author

@zadjii-msft

that is by design

Well, consider this a bad design report then

@zadjii-msft
Copy link
Member

Thanks for the constructive feedback! As I linked above, there's a lot of complicated factors as to why this can't work the way you want, without breaking some other scenario. If you have some idea on how to fix this scenario holistically, I'd be happy to review a PR ☺️

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zadjii-msft @alex-jitbit