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

By default, start in the home folder when opening a linux shell #2462

New Issue
Closed
opened 2026-01-30 22:55:42 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 22:55:42 +00:00
Owner
Copy Link

Originally created by @djk2004 on GitHub (Jul 1, 2019).

Summary of the new feature/enhancement

When opening a new Linux shell, the starting folder is /mnt/c/WINDOWS/system32. Instead, use the current user's home folder. This would match the current behavior with the legacy console.
Generally, most users would not want to work in the system32 folder. However, starting from the home folder would be expected behavior.

Proposed technical implementation details (optional)

Simply change the default starting path to the user's home folder. This could either be the Windows user's home folder, or the Linux shell home folder at /home/. Alternatively, the profile configuration could also include a property that lets the user set the starting folder per profile.

Originally created by @djk2004 on GitHub (Jul 1, 2019). # Summary of the new feature/enhancement When opening a new Linux shell, the starting folder is /mnt/c/WINDOWS/system32. Instead, use the current user's home folder. This would match the current behavior with the legacy console. Generally, most users would not want to work in the system32 folder. However, starting from the home folder would be expected behavior. # Proposed technical implementation details (optional) Simply change the default starting path to the user's home folder. This could either be the Windows user's home folder, or the Linux shell home folder at _/home/<user>_. Alternatively, the profile configuration could also include a property that lets the user set the starting folder per profile.
claunia added the Area-SettingsIssue-TaskResolution-Duplicate labels 2026-01-30 22:55:42 +00:00
claunia commented 2026-01-30 22:55:43 +00:00
Author
Owner
Copy Link

@Kirlac commented on GitHub (Jul 2, 2019):

#592 discusses the configurability of this

There is also a workaround in the comments for that issue - adding ~ to your wsl commandline setting will start in your linux home dir: https://github.com/microsoft/terminal/issues/592#issuecomment-504947429

I agree it would make sense for profiles.json to include this for WSL by default

@Kirlac commented on GitHub (Jul 2, 2019): #592 discusses the configurability of this There is also a workaround in the comments for that issue - adding `~` to your wsl `commandline` setting will start in your linux home dir: https://github.com/microsoft/terminal/issues/592#issuecomment-504947429 I agree it would make sense for `profiles.json` to include this for WSL by default
claunia commented 2026-01-30 22:55:43 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 2, 2019):

Honestly, this should just be a dupe of 592.

@DHowett-MSFT commented on GitHub (Jul 2, 2019): Honestly, this should just be a dupe _of_ 592.
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 Area-Settings Issue-Task 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#2462
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?