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

Enable the user to set the location of settings.json #21519

New Issue
Closed
opened 2026-01-31 07:46:56 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 07:46:56 +00:00
Owner
Copy Link

Originally created by @iwino on GitHub (Apr 14, 2024).

Problem

Currently, the location of settings.json is fixed to be either one of the three locations only:

image

Proposal

Give the user the ability to specify the location via an environment variable, so that the user doesn't have to create any garbage windows shortcut inside some weird folder that ends with some random nonsense like 8wekyb3d8bbwe.

Use case

By allowing the user to specify the location of settings.json cleanly (i.e. without resorting to creating a windows shortcut), it also enables the user to cleanly move it to a folder where the user might have config files for other applications all under one folder.

For example, I use a number of applications on Windows and they all either respect XDG_CONFIG_HOME and/or XDG_DATA_HOME, or provide their own custom environment variables that enable me to move config and data files to a folder of my choice (without having to create garbage shortcuts), making them very easy for me to find as the files are very neatly organized "under one roof".

Originally created by @iwino on GitHub (Apr 14, 2024). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> ## Problem Currently, the location of `settings.json` is fixed to be either one of the three locations only: ![image](https://github.com/microsoft/terminal/assets/128335079/0d1983a4-031b-4a79-8b0e-053a9f60caf5) <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> ## Proposal Give the user the ability to specify the location via an environment variable, so that the user doesn't have to create any garbage windows shortcut inside some weird folder that ends with some random nonsense like `8wekyb3d8bbwe`. ## Use case By allowing the user to specify the location of `settings.json` cleanly (i.e. without resorting to creating a windows shortcut), it also enables the user to cleanly move it to a folder where the user might have config files for other applications all under one folder. For example, I use a number of applications on Windows and they all either respect `XDG_CONFIG_HOME` and/or `XDG_DATA_HOME`, or provide their own custom environment variables that enable me to move config and data files to a folder of my choice (without having to create garbage shortcuts), making them very easy for me to find as the files are very neatly organized "under one roof". <!-- A clear and concise description of what you want to happen. -->
claunia commented 2026-01-31 07:46:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 15, 2024):

FWIW, 8wekyb3d8bbwe actually isn't just "randome nonsense" - it's actually part of the Terminal's unique identifier that we get from the Microsoft Store. %localappdata%\packages\{{package family name}}\LocalState is kinda the well-known path for a package to put their data.

You may also be interested in Portable Mode, though, that lacks the benefit of auto-updating.

Otherwise, we've also got the following threads:

@zadjii-msft commented on GitHub (Apr 15, 2024): FWIW, `8wekyb3d8bbwe` actually isn't just "randome nonsense" - it's actually part of the Terminal's unique identifier that we get from the Microsoft Store. `%localappdata%\packages\{{package family name}}\LocalState` is kinda the well-known path for a package to put their data. You may also be interested in [Portable Mode](https://learn.microsoft.com/en-us/windows/terminal/distributions#windows-terminal-portable), though, that lacks the benefit of auto-updating. Otherwise, we've also got the following threads: * #6687 * #2933
claunia commented 2026-01-31 07:46:58 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Apr 19, 2024):

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.

@microsoft-github-policy-service[bot] commented on GitHub (Apr 19, 2024): 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**. <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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 Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#21519
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?