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

[PR #3547] Enable wt to inherit the working directory #25424

New Issue
Open
opened 2026-01-31 09:09:25 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:09:25 +00:00
Owner
Copy Link

Original Pull Request: https://github.com/microsoft/terminal/pull/3547

State: closed
Merged: No

Summary of the Pull Request

Enable wt to inherit the working directory from the commandline and Explorer.

References

PR Checklist

Detailed Description of the Pull Request / Additional comments

I don't feel totally confident in this change. This changes two scenarios, and the run dialog one I'm not super happy about:

  1. Explorer address bar: wtd -> Results in the Terminal being launched in the current path of explorer.
  2. From a commandline shell: wtd -> Results in the Terminal being launched in the current path of shell.
  3. Windows Search: Win, Term (or anything to get to "Windows Terminal)" -> Results in the Terminal being launched in startingDirectory
  4. Run Dialog: Win+R, wtd -> Results in the Terminal being launched in %USERPROFILE%
  • this is the CWD of the run dialog
  • maybe unexpected?
  1. Windows Search: Win, wtd -> Results in the Terminal being launched in C:\Windows\System32
  • technically, the Start menu is invoking the wtd commandline here.
  • maybe unexpected?
**Original Pull Request:** https://github.com/microsoft/terminal/pull/3547 **State:** closed **Merged:** No --- ## Summary of the Pull Request Enable `wt` to inherit the working directory from the commandline and Explorer. ## References ## PR Checklist * [x] Closes #878 * [x] I work here * [n/a?] Tests added/passed * [n/a] Requires documentation to be updated ## Detailed Description of the Pull Request / Additional comments I don't feel totally confident in this change. This changes two scenarios, and the run dialog one I'm not super happy about: 1. Explorer address bar: `wtd` -> Results in the Terminal being launched in the current path of explorer. 2. From a commandline shell: `wtd` -> Results in the Terminal being launched in the current path of shell. 3. Windows Search: <kbd>Win</kbd>, `Term` (or anything to get to "Windows Terminal)" -> Results in the Terminal being launched in `startingDirectory` 4. Run Dialog: <kbd>Win+R</kbd>, `wtd` -> Results in the Terminal being launched in %USERPROFILE% - this is the CWD of the run dialog - **maybe unexpected?** 5. Windows Search: <kbd>Win</kbd>, `wtd` -> Results in the Terminal being launched in `C:\Windows\System32` - _technically_, the Start menu is invoking the `wtd` commandline here. - **maybe unexpected?**
claunia added the pull-request label 2026-01-31 09:09:25 +00:00
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 pull-request
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#25424
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?