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

Access to adjust defaults/settings #13126

New Issue
Closed
opened 2026-01-31 03:34:30 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 03:34:30 +00:00
Owner
Copy Link

Originally created by @mintyc on GitHub (Mar 21, 2021).

Windows Terminal version (or Windows build number)

10.0.19042.867 1.6.10571.0

Other Software

Latest WSL2 Ubuntu

Steps to reproduce

My end goal is to set the default terminal to an Ubuntu one that has a different StartingDirectory (in WSL$)

I didn't have the Windows Terminal preview, so could not follow
https://docs.microsoft.com/en-us/windows/terminal/customize-settings/startup
Aside:
I did actually install this and use the settings GUI but still couldn't change the starting directory for Ubuntu
It persists as %USERPROFILE% despite attempts to edit and use other forms like
\wsl$\Ubuntu\home\paul (as reported by 'wslpath -w .' in the desired directory
or an escaped equivalent.
Can't get any alternative containing wsl$ to work, so still stuck.

Back to the 'manual' method editing JSON...

Before I follow (conflicting and out of date probably) advice in other threads such as https://github.com/microsoft/terminal/issues/2743 on files to edit, I can't even get into the directory on the windows host to change things.

My understanding is that the json files are in C:\Program Files\WindowsApps\ in a windows terminal sub directory.

I cannot however access to view the WindowsApps directory even as administrator. Controlled by TrustedInstaller and I cannot figure how to access.

Expected Behavior

A sensible, easy to use way to configure the terminal settings - preview version is a good start but doesn't actually seem to help with StartingDirectory - kind of the point

Actual Behavior

A mess of complications, and very difficult to track what is actually going on since many descriptions or older issues no longer apply.

Originally created by @mintyc on GitHub (Mar 21, 2021). ### Windows Terminal version (or Windows build number) 10.0.19042.867 1.6.10571.0 ### Other Software Latest WSL2 Ubuntu ### Steps to reproduce My end goal is to set the default terminal to an Ubuntu one that has a different StartingDirectory (in WSL$) I didn't have the Windows Terminal preview, so could not follow https://docs.microsoft.com/en-us/windows/terminal/customize-settings/startup Aside: I did actually install this and use the settings GUI but still couldn't change the starting directory for Ubuntu It persists as %USERPROFILE% despite attempts to edit and use other forms like \\wsl$\Ubuntu\home\paul (as reported by 'wslpath -w .' in the desired directory or an escaped equivalent. Can't get any alternative containing wsl$ to work, so still stuck. Back to the 'manual' method editing JSON... Before I follow (conflicting and out of date probably) advice in other threads such as https://github.com/microsoft/terminal/issues/2743 on files to edit, I can't even get into the directory on the windows host to change things. My understanding is that the json files are in C:\Program Files\WindowsApps\ in a windows terminal sub directory. I cannot however access to view the WindowsApps directory even as administrator. Controlled by TrustedInstaller and I cannot figure how to access. ### Expected Behavior A sensible, easy to use way to configure the terminal settings - preview version is a good start but doesn't actually seem to help with StartingDirectory - kind of the point ### Actual Behavior A mess of complications, and very difficult to track what is actually going on since many descriptions or older issues no longer apply.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 03:34:30 +00:00
claunia commented 2026-01-31 03:34:31 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 21, 2021):

Huh? When you choose the “Settings” menu item you should be presented with a text editor pointing at the correct settings file. You can put any settings you want (including startingDirectory) into any of the profile blocks in that file.

There is no reason to edit the built-in settings document, as it is only a reference for what Terminal does and is not actually used. Any changes you make to the package folder can destabilize the system (please do not change its ACLs; windows really hates that: #9452).

I don’t understand the assertion that you don’t have preview and that preview doesn’t help with setting the starting directory? It absolutely does have that setting...

@DHowett commented on GitHub (Mar 21, 2021): Huh? When you choose the “Settings” menu item you should be presented with a text editor pointing at the _correct_ settings file. You can put any settings you want (including `startingDirectory`) into any of the profile blocks in that file. There is no reason to edit the built-in settings document, as it is only a reference for what Terminal does and is not actually used. Any changes you make to the package folder can destabilize the system (please do not change its ACLs; windows really hates that: #9452). I don’t understand the assertion that you don’t have preview _and_ that preview doesn’t help with setting the starting directory? It absolutely does have that setting...
claunia commented 2026-01-31 03:34:31 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 21, 2021):

Ah, I understand the preview issue now. The easiest way to help us determine whether there is a bug in settings or in WSL is to try to set the starting directory to something like C:\ and seeing if that sticks. The \\wsl$ network provider is flaky and sometimes fails to work properly.

@DHowett commented on GitHub (Mar 21, 2021): Ah, I understand the preview issue now. The easiest way to help us determine whether there is a bug in settings or in WSL is to try to set the starting directory to something like `C:\` and seeing if that sticks. The `\\wsl$` network provider is flaky and sometimes fails to work properly.
claunia commented 2026-01-31 03:34:31 +00:00
Author
Owner
Copy Link

@mintyc commented on GitHub (Mar 23, 2021):

Ah, I understand the preview issue now. The easiest way to help us determine whether there is a bug in settings or in WSL is to try to set the starting directory to something like C:\ and seeing if that sticks. The \\wsl$ network provider is flaky and sometimes fails to work properly.

Thank you. I will try the preview again and try to change the Ubuntu StartingDirectory to an absolute host path like c:\ rather than the default.

Then I'll try $WSL again but am not hopeful. Not the end of the world to do this manually once inside the terminal window.

@mintyc commented on GitHub (Mar 23, 2021): > Ah, I understand the preview issue now. The easiest way to help us determine whether there is a bug in settings or in WSL is to try to set the starting directory to something like `C:\` and seeing if that sticks. The `\\wsl$` network provider is flaky and sometimes fails to work properly. Thank you. I will try the preview again and try to change the Ubuntu StartingDirectory to an absolute host path like c:\ rather than the default. Then I'll try $WSL again but am not hopeful. Not the end of the world to do this manually once inside the terminal window.
claunia commented 2026-01-31 03:34:31 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 27, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Mar 27, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 03:34:32 +00:00
Author
Owner
Copy Link

@mintyc commented on GitHub (Mar 30, 2021):

No satisfactory auto solution, but easy one liner to manually work around. If nothing else using the preview is highly recommended

@mintyc commented on GitHub (Mar 30, 2021): No satisfactory auto solution, but easy one liner to manually work around. If nothing else using the preview is highly recommended
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 Needs-Attention Needs-Tag-Fix Needs-Triage
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#13126
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?