You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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
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
Environment
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
The text was updated successfully, but these errors were encountered: