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

Open WT in selected directory by default (e.g. User Homd directory) #15985

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

Originally created by @Zingam on GitHub (Nov 27, 2021).

If WT is opened from a shortcut I would prefer if the default directory is set to user's desktop directory or user's home directory and in any other case to the process directory, like when opening it via right click on a folder or by typing WT in Explorer.
Currently with this setting (Use process directory) WT opens by default: C:/Windows/System32 which is probably the last place I need it to open. So I think in this case it would be much more useful if by default WT opens C:/Users/<User's home> or some other preset location.

Currently I don't see how I can achieve that. If I set %USERPROFILE% then I loose the ability to open WT directly in any other location.

Originally created by @Zingam on GitHub (Nov 27, 2021). If WT is opened from a shortcut I would prefer if the default directory is set to user's desktop directory or user's home directory and in any other case to the process directory, like when opening it via right click on a folder or by typing WT in Explorer. Currently with this setting (Use process directory) WT opens by default: C:/Windows/System32 which is probably the last place I need it to open. So I think in this case it would be much more useful if by default WT opens C:/Users/<User's home> or some other preset location. Currently I don't see how I can achieve that. If I set %USERPROFILE% then I loose the ability to open WT directly in any other location.
claunia commented 2026-01-31 04:54:06 +00:00
Author
Owner
Copy Link

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

This is an unfortunately complicated problem, with a lot more details in

So, I'd recommend leaving startingDirectory set to %USERPROFILE%, and manually adding -d . to the commandline for your shortcuts. That'll get you the behavior you want:

  • shortcuts will open up in the surrent directory
  • right-click in explorer will open up in explorer's CWD
  • launching from the Start Menu, Taskbar, etc, will launch in %USERPROFILE%
@zadjii-msft commented on GitHub (Nov 29, 2021): This is an unfortunately complicated problem, with a lot more details in * https://github.com/microsoft/terminal/issues/878#issuecomment-538511693 * https://github.com/microsoft/terminal/pull/3547 * https://github.com/microsoft/terminal/issues/878#issuecomment-579508860 So, I'd recommend leaving `startingDirectory` set to `%USERPROFILE%`, and manually adding `-d .` to the commandline for your shortcuts. That'll get you the behavior you want: * shortcuts will open up in the surrent directory * right-click in explorer will open up in explorer's CWD * launching from the Start Menu, Taskbar, etc, will launch in `%USERPROFILE%`
claunia commented 2026-01-31 04:54:06 +00:00
Author
Owner
Copy Link

@Zingam commented on GitHub (Nov 29, 2021):

This doesn't solve the issue to open a terminal via File Explorer's (address bar??) that I learned to use instead of adding Command Prompt to the right click menu via the registry a long time ago. Yet the proposed solutions sound like a good start. Why don't you create this configuration and short cuts by default during installation? At least this wasn't the case when I installed WT.

@Zingam commented on GitHub (Nov 29, 2021): This doesn't solve the issue to open a terminal via File Explorer's (address bar??) that I learned to use instead of adding Command Prompt to the right click menu via the registry a long time ago. Yet the proposed solutions sound like a good start. Why don't you create this configuration and short cuts by default during installation? At least this wasn't the case when I installed WT.
claunia commented 2026-01-31 04:54:06 +00:00
Author
Owner
Copy Link

@Zingam commented on GitHub (Nov 29, 2021):

So, I'd recommend leaving startingDirectory set to %USERPROFILE%, and manually adding -d . to the commandline for

OK. I guess -d . is meand for File Explorer bar. What about introducing an alternative alias for that like 'wtd', which will do what wt -d . It may not look that much shorter but in the long term it save the planet from overheating.

Thank you for taking the time to answer my issue!

@Zingam commented on GitHub (Nov 29, 2021): > So, I'd recommend leaving `startingDirectory` set to `%USERPROFILE%`, and manually adding `-d .` to the commandline for OK. I guess -d . is meand for File Explorer bar. What about introducing an alternative alias for that like 'wtd', which will do what wt -d . It may not look that much shorter but in the long term it save the planet from overheating. Thank you for taking the time to answer my issue!
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 Issue-Question Needs-Tag-Fix Needs-Triage 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#15985
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?