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

Behavior when started in the address bar of explorer #8325

New Issue
Closed
opened 2026-01-31 01:26:33 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 01:26:33 +00:00
Owner
Copy Link

Originally created by @taroxd on GitHub (May 20, 2020).

Description of the new feature/enhancement

Currently, when entering wt in the address bar of explorer, the terminal opens with current directory being my home directory.

Screenshot

That is not the case when entering cmd or wsl, where the current directory would be changed to the directory in the explorer. One workaround is typing wt -d . in the address bar, but that seems rather redundant.

Also, I think it would be better to open a new tab (instead of a new window) in an existing Windows Terminal window when there is such a window available. I suggest adding a configurable option to toggle this behavior.

Originally created by @taroxd on GitHub (May 20, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement Currently, when entering `wt` in the address bar of explorer, the terminal opens with current directory being my home directory. ![Screenshot](https://user-images.githubusercontent.com/6070540/82436679-cbb51380-9ac8-11ea-8880-1ae289bb1fc9.png) That is not the case when entering `cmd` or `wsl`, where the current directory would be changed to the directory in the explorer. One workaround is typing `wt -d .` in the address bar, but that seems rather redundant. Also, I think it would be better to open a new tab (instead of a new window) in an existing Windows Terminal window when there is such a window available. I suggest adding a configurable option to toggle this behavior.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 01:26:34 +00:00
claunia commented 2026-01-31 01:26:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 20, 2020):

Thanks for the suggestion! We wanted to make wt behave like cmd or powershell here, but unfortunately, there were just too many odd edge cases to make this work right. There are more details over in https://github.com/microsoft/terminal/issues/878#issuecomment-579508860 if you want more reading.

As far as opening a new tab in the existing window, I'd follow #4472

/dup #878

/dup #4472

@zadjii-msft commented on GitHub (May 20, 2020): Thanks for the suggestion! We wanted to make `wt` behave like `cmd` or `powershell` here, but unfortunately, there were just too many odd edge cases to make this work right. There are more details over in https://github.com/microsoft/terminal/issues/878#issuecomment-579508860 if you want more reading. As far as opening a new tab in the existing window, I'd follow #4472 /dup #878 /dup #4472
claunia commented 2026-01-31 01:26:35 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 20, 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 commented on GitHub (May 20, 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!
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 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#8325
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?