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

Typing "wt" in File Explorer's address bar (while browsing a file folder) opens Terminal but does not browse the current folder. CMD works. #4647

Closed
shanselman opened this issue Feb 19, 2020 · 8 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@shanselman
Copy link
Member

Environment

Windows build number: Microsoft Windows [Version 10.0.19041.84]
Windows Terminal version (if applicable): 0.9.433.0 (but N/A)

Steps to reproduce

Typing "wt" in File Explorer's address bar (while browsing a file folder) opens Terminal but does not browse the current folder. CMD works.

image
Click in the address bar in Explorer, type wt and press enter. This works with cmd, not with wt.

image

Expected behavior

I'd expect wt to imply -d in this context and work the same way cmd does.

Actual behavior

Terminal just opens at the default starting directory.

@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 19, 2020
@Wason1797
Copy link

Wason1797 commented Feb 19, 2020

@shanselman I think this was discussed here: #620

@carlinmack I don't think that's entirely necessary.

  • If you launch wt from the Windows Explorer address bar, or via something like cmd.exe (or another shell) navigated to a certain folder, then the "startingDirectory": "." will ensure that Windows Terminal opens in the directory you were in.

Maybe you can look at https://gist.github.com/akunzai/b4b1f394db3ceb399ba1976a30e540fa#file-profiles-json-L9
It worked for me.

@zadjii-msft
Copy link
Member

@shanselman there's like so much discussion on this in /dupe #878, please search before filing new issues 😜

@ghost
Copy link

ghost commented Feb 19, 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 19, 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 19, 2020
@shanselman
Copy link
Member Author

Sorry for that. I just think that #878 (comment) isn't really an acceptable answer. :(

@shanselman
Copy link
Member Author

So, @zadjii-msft this worked for me #4647 (comment) why don't we promote/do that?

@zadjii-msft
Copy link
Member

@shanselman Because if you do that, then launching the Terminal from the Start Menu starts up in C:\Windows\System32. There's no way to have the app launch in a reasonable starting directory from both the Start Menu and also from the address bar of explorer.exe

@shanselman
Copy link
Member Author

I literally just launched wt from Win+R just now and it shows up in C:\Users\scott

@Banyc
Copy link

Banyc commented Aug 8, 2020

TL, DR;

Go to the settings of wt, add one line like the following:

            {
                "guid": "{...}",
                "hidden": false,
                "name": "PowerShell",
                "source": "Windows.Terminal.PowershellCore",
                "startingDirectory": "./"
            },

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

4 participants