starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

wt shortcut not opening in the requested context from Address bar when Starting directory option is customized #15948

New Issue
Closed
opened 2026-01-31 04:53:09 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 04:53:09 +00:00
Owner
Copy Link

Originally created by @egvijayanand on GitHub (Nov 22, 2021).

Windows Terminal version

1.11.2921.0

Windows build number

10.0.22000.348

Other Software

No response

Steps to reproduce

  • Customize the Starting directory for the Command Prompt tab in Windows Terminal Settings
  • Open any folder (apart from Starting directory) in the File Explorer and type wt in the address bar to launch the Terminal
  • Fails to persist the launch context and instead opens with the Starting directory

Expected Behavior

During the launch, the Terminal should retain the launch context for specific scenarios like Address bar launch and Context menu launch

Actual Behavior

Always opens with the Starting directory customization, this is fine for direct launch whereas when launched from the address bar or from the context menu of a folder, then it is expected to retain the launch context.

Originally created by @egvijayanand on GitHub (Nov 22, 2021). ### Windows Terminal version 1.11.2921.0 ### Windows build number 10.0.22000.348 ### Other Software _No response_ ### Steps to reproduce * Customize the `Starting directory` for the `Command Prompt` tab in Windows Terminal `Settings` * Open any folder (apart from Starting directory) in the File Explorer and type `wt` in the address bar to launch the Terminal * Fails to persist the launch context and instead opens with the Starting directory ### Expected Behavior During the launch, the Terminal should retain the launch context for specific scenarios like Address bar launch and Context menu launch ### Actual Behavior Always opens with the `Starting directory` customization, this is fine for direct launch whereas when launched from the address bar or from the context menu of a folder, then it is expected to retain the launch context.
claunia added the Resolution-Duplicate label 2026-01-31 04:53:09 +00:00
claunia commented 2026-01-31 04:53:10 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 22, 2021):

This question's been answered a huge number of times before. Please search before filing new issues.

/dup #878

Specifically, there are more details as to "why" here: https://github.com/microsoft/terminal/issues/878#issuecomment-579508860

@zadjii-msft commented on GitHub (Nov 22, 2021): This question's been answered a huge number of times before. Please [search before filing new issues. ](https://github.com/microsoft/terminal/issues?q=is%3Aissue+%22explorer+address+bar%22) /dup #878 Specifically, there are more details as to "why" here: https://github.com/microsoft/terminal/issues/878#issuecomment-579508860
claunia commented 2026-01-31 04:53:10 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 22, 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 commented on GitHub (Nov 22, 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!
claunia commented 2026-01-31 04:53:10 +00:00
Author
Owner
Copy Link

@egvijayanand commented on GitHub (Dec 1, 2021):

Hope the original issue #878 gets an official resolution at the earliest.

For time being, found a workaround by creating a batch file in the profile folder (so that it is available whenever I log in) with the below command in it to invoke the Windows Terminal with the right starting directory.

Name the batch file, like wtd.bat, as per your convenience as that will become the command to execute on the address bar, wtd in this case.

wt.exe --startingDirectory "%cd%"
@egvijayanand commented on GitHub (Dec 1, 2021): Hope the original issue #878 gets an official resolution at the earliest. For time being, found a workaround by creating a batch file in the profile folder (so that it is available whenever I log in) with the below command in it to invoke the `Windows Terminal` with the right starting directory. Name the batch file, like wtd.bat, as per your convenience as that will become the command to execute on the address bar, `wtd` in this case. ``` wt.exe --startingDirectory "%cd%" ```
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 Resolution-Duplicate
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#15948
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?