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

Support linux paths for startingDirectory of WSL distros #850

New Issue
Open
opened 2026-01-30 22:06:24 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 22:06:24 +00:00
Owner
Copy Link

Originally created by @tackyunicorn on GitHub (May 8, 2019).

Originally assigned to: @DHowett on GitHub.

  • Your Windows build number: Microsoft Windows [Version 10.0.18362.86]

  • What you're doing and what's happening:
    Setting the starting directory for wsl in profiles.json doesn't make it point to the right directory.

  1. Take the config below :-
{
        "startingDirectory": "C:/Users/joshj/AppData/Local/Packages/CanonicalGroupLimited.Ubuntu16.04onWindows_79rhkp1fndgsc/LocalState/rootfs/home/tackyunicorn",
        "guid": "{a2785f8e-72c9-4550-b406-697388644902}",
        "name": "Ubuntu",
        "colorscheme": "MonokaiVivid",
        "historySize": 9001,
        "snapOnInput": true,
        "cursorColor": "#FFFFFF",
        "cursorHeight": 25,
        "cursorShape": "vintage",
        "commandline": "wsl.exe",
        "fontFace": "Inconsolata for Powerline",
        "fontSize": 10,
        "acrylicOpacity": 1,
        "useAcrylic": true,
        "closeOnExit": true,
        "padding": "10, 10, 10, 10",
        "icon": "ms-appdata:///roaming/ubuntu.png"
}

This results in wsl starting up in the root folder
issue1

  1. In this config :-
{
        "startingDirectory": "/home/tackyunicorn",
        "guid": "{a2785f8e-72c9-4550-b406-697388644902}",
        "name": "Ubuntu",
        "colorscheme": "MonokaiVivid",
        "historySize": 9001,
        "snapOnInput": true,
        "cursorColor": "#FFFFFF",
        "cursorHeight": 25,
        "cursorShape": "vintage",
        "commandline": "wsl.exe",
        "fontFace": "Inconsolata for Powerline",
        "fontSize": 10,
        "acrylicOpacity": 1,
        "useAcrylic": true,
        "closeOnExit": true,
        "padding": "10, 10, 10, 10",
        "icon": "ms-appdata:///roaming/ubuntu.png"
}

This results in wsl starting up in the Windows user folder
issue2

  • What's wrong / what should be happening instead:
    The startingDirectory profile setting is not being applied correctly on a wsl profile
Originally created by @tackyunicorn on GitHub (May 8, 2019). Originally assigned to: @DHowett on GitHub. * Your Windows build number: `Microsoft Windows [Version 10.0.18362.86]` * What you're doing and what's happening: Setting the starting directory for wsl in `profiles.json` doesn't make it point to the right directory. 1. Take the config below :- ```json { "startingDirectory": "C:/Users/joshj/AppData/Local/Packages/CanonicalGroupLimited.Ubuntu16.04onWindows_79rhkp1fndgsc/LocalState/rootfs/home/tackyunicorn", "guid": "{a2785f8e-72c9-4550-b406-697388644902}", "name": "Ubuntu", "colorscheme": "MonokaiVivid", "historySize": 9001, "snapOnInput": true, "cursorColor": "#FFFFFF", "cursorHeight": 25, "cursorShape": "vintage", "commandline": "wsl.exe", "fontFace": "Inconsolata for Powerline", "fontSize": 10, "acrylicOpacity": 1, "useAcrylic": true, "closeOnExit": true, "padding": "10, 10, 10, 10", "icon": "ms-appdata:///roaming/ubuntu.png" } ``` This results in wsl starting up in the root folder ![issue1](https://user-images.githubusercontent.com/26558907/57397677-d9179c80-71ea-11e9-9f35-a1176a5368d8.png) 2. In this config :- ```json { "startingDirectory": "/home/tackyunicorn", "guid": "{a2785f8e-72c9-4550-b406-697388644902}", "name": "Ubuntu", "colorscheme": "MonokaiVivid", "historySize": 9001, "snapOnInput": true, "cursorColor": "#FFFFFF", "cursorHeight": 25, "cursorShape": "vintage", "commandline": "wsl.exe", "fontFace": "Inconsolata for Powerline", "fontSize": 10, "acrylicOpacity": 1, "useAcrylic": true, "closeOnExit": true, "padding": "10, 10, 10, 10", "icon": "ms-appdata:///roaming/ubuntu.png" } ``` This results in wsl starting up in the Windows user folder ![issue2](https://user-images.githubusercontent.com/26558907/57398045-ba65d580-71eb-11e9-9109-79a9ad601e12.png) * What's wrong / what should be happening instead: The `startingDirectory` profile setting is not being applied correctly on a wsl profile
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 Area-TerminalControl Help Wanted Issue-Feature Product-Terminal Resolution-Fix-Committed
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#850
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?