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

How can I change the default location of the settings.json file? #14309

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

Originally created by @iamadiscordbot on GitHub (Jun 22, 2021).

I like to keep all my dotfiles in one place to upload it to github, and the settings.json is located in a way different location. I would like to change it to a different location so that it would be more convenient for me to upload the dotfiles to github.

Ps- I use WSL so I want to move it to the ~/.config folder.

Originally created by @iamadiscordbot on GitHub (Jun 22, 2021). I like to keep all my dotfiles in one place to upload it to github, and the settings.json is located in a way different location. I would like to change it to a different location so that it would be more convenient for me to upload the dotfiles to github. Ps- I use WSL so I want to move it to the ~/.config folder.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 04:06:52 +00:00
claunia commented 2026-01-31 04:06:53 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Jun 22, 2021):

The location of settings.json is an implementation detail and can't be moved. It's possible to add logic that allows users to specify the path but while many users like myself use WSL with WT, there are plenty of users who don't use WSL, so moving it doesn't make sense for them. Also, the regeneration logic would be a more difficult piece to account for. If it's not where you said it is, should WT create a new file? What if that file exists elsewhere on the system? Then it becomes "WT searches everywhere for settings.json and if not found, create one at the specified path if one is provided", which would be expensive on filesystem performance on top of waiting for WT to finish searching for it to even start up. Better that it remains where it is.

@WSLUser commented on GitHub (Jun 22, 2021): The location of settings.json is an implementation detail and can't be moved. It's possible to add logic that allows users to specify the path but while many users like myself use WSL with WT, there are plenty of users who don't use WSL, so moving it doesn't make sense for them. Also, the regeneration logic would be a more difficult piece to account for. If it's not where you said it is, should WT create a new file? What if that file exists elsewhere on the system? Then it becomes "WT searches everywhere for settings.json and if not found, create one at the specified path if one is provided", which would be expensive on filesystem performance on top of waiting for WT to finish searching for it to even start up. Better that it remains where it is.
claunia commented 2026-01-31 04:06:53 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 6, 2021):

Thanks for the request! We're generally tracking this request in #2933. That issue might refer to "roaming settings", but it's kinda evolved to the general "import settings from other paths" tracker.

/dup #2933

@zadjii-msft commented on GitHub (Jul 6, 2021): Thanks for the request! We're generally tracking this request in #2933. That issue might refer to "roaming settings", but it's kinda evolved to the general "import settings from other paths" tracker. /dup #2933
claunia commented 2026-01-31 04:06:53 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 6, 2021):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jul 6, 2021): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 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#14309
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?