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

The location of settings.json should be configurable so that it can be place in .dotfiles or a soft-link to it #15120

New Issue
Closed
opened 2026-01-31 04:29:11 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 04:29:11 +00:00
Owner
Copy Link

Originally created by @kasajian on GitHub (Sep 7, 2021).

I had been putting it off, but now I'm attempting to move from ConsoleZ to Windows Terminal. One feature that I feel is essential is the ability for me to share my settings across my computers and also share my settings with others, the way .dotfiles are often shared publicly on github. I have other settings there such as my vim plugins, etc.

So I would like to have a well-known location for settings.json that Windows Terminal uses. On my computer it's located here: C:\Users...\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json

The name WindowsTerminal_8wekyb3d8bbwe looks sus. That seems like it might be a version and/or installation specific. ConsoleZ's setting had to be in it's own location, but I could use a soft-link to it from my .dotfiles folder.

My suggestion is to use a common convention of putting such settings in a well known location such as %userprofile%.windowsterminal...
or something like that.

If there's another way to solve this, I'd love to know about it.

Originally created by @kasajian on GitHub (Sep 7, 2021). I had been putting it off, but now I'm attempting to move from ConsoleZ to Windows Terminal. One feature that I feel is essential is the ability for me to share my settings across my computers and also share my settings with others, the way .dotfiles are often shared publicly on github. I have other settings there such as my vim plugins, etc. So I would like to have a well-known location for settings.json that Windows Terminal uses. On my computer it's located here: C:\Users\...\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json The name WindowsTerminal_8wekyb3d8bbwe looks sus. That seems like it might be a version and/or installation specific. ConsoleZ's setting had to be in it's own location, but I could use a soft-link to it from my .dotfiles folder. My suggestion is to use a common convention of putting such settings in a well known location such as %userprofile%\.windowsterminal\... or something like that. If there's another way to solve this, I'd love to know about it.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 04:29:11 +00:00
claunia commented 2026-01-31 04:29:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 7, 2021):

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #2933 for more discussion.

/dup #2933

@zadjii-msft commented on GitHub (Sep 7, 2021): Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #2933 for more discussion. /dup #2933
claunia commented 2026-01-31 04:29:12 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 7, 2021):

Couple notes before I close this out as a duplicate!

  1. The path is based on an intrinsic property of our application package, and is constant for every user and every install (separated by Preview or Stable version)!
  2. You can replace settings.json with a symbolic link, and Terminal will keep working just fine. This has worked pretty well for people in the past.
@DHowett commented on GitHub (Sep 7, 2021): Couple notes before I close this out as a duplicate! 1. The path is based on an intrinsic property of our application package, and is constant for every user and every install (separated by Preview or Stable version)! 2. You can replace settings.json with a symbolic link, and Terminal will keep working just fine. This has worked pretty well for people in the past.
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#15120
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?