starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

When opening wt from explorer in the address bar it should set the current directory as working directory #9101

New Issue
Closed
opened 2026-01-31 01:46:05 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 01:46:05 +00:00
Owner
Copy Link

Originally created by @allancm on GitHub (Jun 18, 2020).

When the explorer is used, you can write a command in the address bar.
If you use cmd.exe or only cmd, a new window with the cmd is opened and the current directory of that console is pointing to the directory where the explorer is pointing.
It would be very useful if you write wt.exe or only wt, and the new windows terminal is opened with the current directory as the directory where the explorer is pointing.
Currently the window terminal is heading to a fixed directory no matter where you started the command "wt".

Proposed technical implementation details (optional)

I would use something similar as launch the powershell.exe -NoExit -command "& {Set-Location EXPLORERPATH}" but with the wt.exe,

Step1
Step2
Step3
Step4
Step5
Step6

Thanks in advance

Originally created by @allancm on GitHub (Jun 18, 2020). When the explorer is used, you can write a command in the address bar. If you use cmd.exe or only cmd, a new window with the cmd is opened and the current directory of that console is pointing to the directory where the explorer is pointing. It would be very useful if you write wt.exe or only wt, and the new windows terminal is opened with the current directory as the directory where the explorer is pointing. Currently the window terminal is heading to a fixed directory no matter where you started the command "wt". # Proposed technical implementation details (optional) I would use something similar as launch the powershell.exe -NoExit -command "& {Set-Location EXPLORERPATH}" but with the wt.exe, ![Step1](https://user-images.githubusercontent.com/2113118/84983134-5bb0a200-b0f5-11ea-82cd-99afb60dd979.png) ![Step2](https://user-images.githubusercontent.com/2113118/84983136-5c493880-b0f5-11ea-8d8d-66e47a0fac5f.png) ![Step3](https://user-images.githubusercontent.com/2113118/84983139-5d7a6580-b0f5-11ea-82e8-90d9e8d1e943.png) ![Step4](https://user-images.githubusercontent.com/2113118/84983141-5e12fc00-b0f5-11ea-8fae-1c7ce6b5280a.png) ![Step5](https://user-images.githubusercontent.com/2113118/84983142-5e12fc00-b0f5-11ea-8dfe-0f3e8e957937.png) ![Step6](https://user-images.githubusercontent.com/2113118/84983143-5f442900-b0f5-11ea-9b56-a4f8d6da5eb8.png) Thanks in advance
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 01:46:05 +00:00
claunia commented 2026-01-31 01:46:06 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 18, 2020):

So, there’s a limitation here that we’ve worked around by enforcing a startup directory as part of each profile. You can run WT in the current directory by entering wt -d .

More info in #3547 (PR Description)

@DHowett commented on GitHub (Jun 18, 2020): So, there’s a limitation here that we’ve worked around by enforcing a startup directory as part of each profile. You can run WT in the current directory by entering `wt -d .` More info in #3547 (PR Description)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Needs-Tag-Fix Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#9101
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?