documentation is unclear about being able to use wt.exe #5766

Closed
opened 2026-01-31 00:21:07 +00:00 by claunia · 4 comments
Owner

Originally created by @BananaAcid on GitHub (Jan 4, 2020).

Originally assigned to: @cinnamon-msft on GitHub.

It would be helpful, to have wt.exe being mentioned in the Readme.md.

While creating an issue on not being able to find out how to run it from commandline, I found a closed issue already about it - others had the same issue finding info about it already.

Originally created by @BananaAcid on GitHub (Jan 4, 2020). Originally assigned to: @cinnamon-msft on GitHub. It would be helpful, to have `wt.exe` being mentioned in the `Readme.md`. While creating an issue on not being able to find out how to run it from commandline, I found a closed issue already about it - others had the same issue finding info about it already.
claunia added the Area-SettingsNeeds-Tag-FixIssue-DocsProduct-Meta labels 2026-01-31 00:21:07 +00:00
Author
Owner

@KharmaScribbles commented on GitHub (Jan 6, 2020):

Also, if you set

"startingDirectory": .

in settings, you can use "wt.exe" in File Explorer's path bar and start inside the directory File Explorer was in.

@KharmaScribbles commented on GitHub (Jan 6, 2020): Also, if you set "startingDirectory": . in settings, you can use "wt.exe" in File Explorer's path bar and start inside the directory File Explorer was in.
Author
Owner

@BananaAcid commented on GitHub (Jan 6, 2020):

How does "use [...] in File Explorer's path bar" work? Typing the exe into it does not.

@BananaAcid commented on GitHub (Jan 6, 2020): How does "use [...] in File Explorer's path bar" work? Typing the exe into it does not.
Author
Owner

@KharmaScribbles commented on GitHub (Jan 6, 2020):

How does "use [...] in File Explorer's path bar" work? Typing the exe into it does not.

Please ensure you've set "StartingDir" to the value= . (that is a period, btw) in your profiles.json and start a new shell.

Go to File Explorer, pick an accessible directory by clicking into it as normal, then:

wt

Click into File Explorer's 'address bar and type "wt.exe" (no quotes, see above image) and press enter.

Give it a moment to start up, but when it does it should be in the same directory that File Explorer was :)

@KharmaScribbles commented on GitHub (Jan 6, 2020): > How does "use [...] in File Explorer's path bar" work? Typing the exe into it does not. Please ensure you've set "StartingDir" to the value= . (that is a period, btw) in your profiles.json and start a new shell. Go to File Explorer, pick an accessible directory by clicking into it as normal, then: ![wt](https://user-images.githubusercontent.com/36386908/71796377-80adce80-3007-11ea-90b2-9fcb433dd7cc.png) Click into File Explorer's 'address bar and type "wt.exe" (no quotes, see above image) and press enter. Give it a moment to start up, but when it does it should be in the same directory that File Explorer was :)
Author
Owner

@zadjii-msft commented on GitHub (Dec 9, 2021):

You know, it's been a few years now, and the docs have actually gotten pretty good now: https://docs.microsoft.com/en-us/windows/terminal/command-line-arguments?tabs=windows

(I believe when this was originally filed, we didn't have a docs repo yet 😋)

I'm gonna close this one out. Thanks!

@zadjii-msft commented on GitHub (Dec 9, 2021): You know, it's been a few years now, and the docs have actually gotten pretty good now: https://docs.microsoft.com/en-us/windows/terminal/command-line-arguments?tabs=windows (I believe when this was originally filed, we didn't have a docs repo yet 😋) I'm gonna close this one out. Thanks!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#5766