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

wt doesn't start in directory given from explorer #8672

Closed
csm10495 opened this issue Dec 28, 2020 · 3 comments
Closed

wt doesn't start in directory given from explorer #8672

csm10495 opened this issue Dec 28, 2020 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@csm10495
Copy link

Environment

Windows build number: 10.0.18363.1256
Windows Terminal version (if applicable): 1.4.3243.0

Any other software?

I don't think it matters but I am using clink in cmd and a profile in powershell. Same stuff happens without them.

Steps to reproduce

If I open wt from a directory via Windows Explorer, it doesn't start in the correct directory. This behavior is different from cmd/powershell.

Expected behavior

If i run wt in Windows Explorer in a directory, it should start in that directory.

Actual behavior

wt seems to start in the user's home directory.

Attaching a video of the behavior difference

cwd_bug.mp4
@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 Dec 28, 2020
@j4james
Copy link
Collaborator

j4james commented Dec 28, 2020

The recommended way to make this work is by entering wt -d . in the explorer bar. For more info see #878 (comment).

@zadjii-msft
Copy link
Member

Yep, this is by design. /dup #878

@ghost
Copy link

ghost commented Jan 3, 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 Jan 3, 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 Jan 3, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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