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

WT does not open in the current folder when typing 'wt' in the File Explorer address bar #11155

New Issue
Closed
opened 2026-01-31 02:40:07 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 02:40:07 +00:00
Owner
Copy Link

Originally created by @claudiofreda on GitHub (Oct 24, 2020).

A very common shortcut to open a powershell or cmd window in the current File Explorer folder is to type 'cmd' or 'powershell' into the address bar. This passes the current folder as an argument to the shell, which opens alread cd'd into that folder.

This does not work with windows terminal, and typing 'wt' into the address bar results into opening 'wt' with the user home folder as current directory.

Surprisingly, this even works for WSL prompts.

I argue this is a desirable feature and behaviour and should be introduced to Windows Terminal.

Originally created by @claudiofreda on GitHub (Oct 24, 2020). A very common shortcut to open a powershell or cmd window in the current File Explorer folder is to type 'cmd' or 'powershell' into the address bar. This passes the current folder as an argument to the shell, which opens alread cd'd into that folder. This does not work with windows terminal, and typing 'wt' into the address bar results into opening 'wt' with the user home folder as current directory. Surprisingly, this even works for WSL prompts. I argue this is a desirable feature and behaviour and should be introduced to Windows Terminal.
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 02:40:07 +00:00
claunia commented 2026-01-31 02:40:08 +00:00
Author
Owner
Copy Link

@obsgolem commented on GitHub (Oct 26, 2020):

This feature does exist, it is just not enabled by default. To enable it, add

"startingDirectory" : ".",

to your default profile.

@obsgolem commented on GitHub (Oct 26, 2020): This feature does exist, it is just not enabled by default. To enable it, add ``` "startingDirectory" : ".", ``` to your default profile.
claunia commented 2026-01-31 02:40:08 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 26, 2020):

Or, you can run wt -d .. This has been discussed in a bunch of places on our repo, and none of the solutions we can offer are quite beloved. 😄

@DHowett commented on GitHub (Oct 26, 2020): Or, you can run `wt -d .`. This has been discussed in a bunch of places on our repo, and none of the solutions we can offer are quite beloved. :smile:
claunia commented 2026-01-31 02:40:08 +00:00
Author
Owner
Copy Link

@Lycantant commented on GitHub (Nov 6, 2020):

This feature does exist, it is just not enabled by default. To enable it, add

"startingDirectory" : ".",

to your default profile.

Or, you can run wt -d .. This has been discussed in a bunch of places on our repo, and none of the solutions we can offer are quite beloved. 😄

thanks, it work 😁

@Lycantant commented on GitHub (Nov 6, 2020): > > > This feature does exist, it is just not enabled by default. To enable it, add > > ``` > "startingDirectory" : ".", > ``` > > to your default profile. > > > Or, you can run `wt -d .`. This has been discussed in a bunch of places on our repo, and none of the solutions we can offer are quite beloved. 😄 thanks, it work 😁
claunia commented 2026-01-31 02:40:09 +00:00
Author
Owner
Copy Link

@ahmed-el-awad commented on GitHub (Apr 8, 2024):

This feature does exist, it is just not enabled by default. To enable it, add

"startingDirectory" : ".",

to your default profile.

For anyone reading this in the future, in settings.json you should add it here.

"profiles": {
    "defaults": {
      "startingDirectory": ".",
      ...
      }
  }

Not at the top of settings.json (like I assumed).
I got this solution from https://superuser.com/a/1528644/1837537.

@ahmed-el-awad commented on GitHub (Apr 8, 2024): > This feature does exist, it is just not enabled by default. To enable it, add > > ``` > "startingDirectory" : ".", > ``` > > to your default profile. For anyone reading this in the future, in `settings.json` you should add it here. ``` "profiles": { "defaults": { "startingDirectory": ".", ... } } ``` Not at the top of `settings.json` (like I assumed). I got this solution from https://superuser.com/a/1528644/1837537.
claunia commented 2026-01-31 02:40:09 +00:00
Author
Owner
Copy Link

@claudiofreda commented on GitHub (May 6, 2024):

I guess the question that naturally comes to mind is: why isn't this default?

@claudiofreda commented on GitHub (May 6, 2024): I guess the question that naturally comes to mind is: why isn't this default?
claunia commented 2026-01-31 02:40:09 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 6, 2024):

@claudiofreda There's commentary in #3547, #878, and the very many linked threads as to why this is the way it is.

@zadjii-msft commented on GitHub (May 6, 2024): @claudiofreda There's commentary in #3547, #878, and the very many linked threads as to why this is the way it is.
claunia commented 2026-01-31 02:40:09 +00:00
Author
Owner
Copy Link

@thedarkfalcon commented on GitHub (Nov 12, 2024):

@zadjii-msft you posted links to threads where everyone hates the behaviour. Opening in a users home directory is to prevent it from opening in system32. But always opening in users home directory is worse behaviour in my opinion than opening in the current directory. CMD opens in system32 by default, but also opens in whatever directory you launch it from, this is far preferable in my opinion.

@thedarkfalcon commented on GitHub (Nov 12, 2024): @zadjii-msft you posted links to threads where everyone hates the behaviour. Opening in a users home directory is to prevent it from opening in system32. But always opening in users home directory is worse behaviour in my opinion than opening in the current directory. CMD opens in system32 by default, but also opens in whatever directory you launch it from, this is far preferable in my opinion.
claunia commented 2026-01-31 02:40:09 +00:00
Author
Owner
Copy Link

@avail commented on GitHub (Apr 24, 2025):

this only started happening with 1.23.
https://github.com/user-attachments/assets/18eea4e9-dd59-4486-827e-62353607da4a

@avail commented on GitHub (Apr 24, 2025): this only started happening with 1.23. https://github.com/user-attachments/assets/18eea4e9-dd59-4486-827e-62353607da4a
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-Question Needs-Tag-Fix Resolution-Answered
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#11155
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?