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

configuration json path change to document path #23555

New Issue
Closed
opened 2026-01-31 08:45:49 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 08:45:49 +00:00
Owner
Copy Link

Originally created by @CN-CODEGOD on GitHub (Aug 27, 2025).

Description of the new feature

Hello, why doesn't we change the json path to document $home\document\terminal\config.json?

Proposed technical implementation details

i could use onedrive to save/export the setting easily if so.
No response

Originally created by @CN-CODEGOD on GitHub (Aug 27, 2025). ### Description of the new feature Hello, why doesn't we change the json path to document $home\document\terminal\config.json? ### Proposed technical implementation details i could use onedrive to save/export the setting easily if so. _No response_
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 08:45:49 +00:00
claunia commented 2026-01-31 08:45:50 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 27, 2025):

Because it is not a document! Just because other poorly-behaved applications store configuration files there, does not mean that we should.

@DHowett commented on GitHub (Aug 27, 2025): Because it is not a document! Just because other poorly-behaved applications store configuration files there, does not mean that we should.
claunia commented 2026-01-31 08:45:50 +00:00
Author
Owner
Copy Link

@CN-CODEGOD commented on GitHub (Aug 27, 2025):

Because it is not a document! Just because other poorly-behaved applications store configuration files there, does not mean that we should.

hello,i don't understand why ,if there is something specific to put the files in a different path from install path which hard to navigate.if there is a posible way to easy export the setting

@CN-CODEGOD commented on GitHub (Aug 27, 2025): > Because it is not a document! Just because other poorly-behaved applications store configuration files there, does not mean that we should. hello,i don't understand why ,if there is something specific to put the files in a different path from install path which hard to navigate.if there is a posible way to easy export the setting
claunia commented 2026-01-31 08:45:51 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Aug 27, 2025):

We're tracking this in #2933. We're happy to accept any contributions for that issue. 🙂

@lhecker commented on GitHub (Aug 27, 2025): We're tracking this in #2933. We're happy to accept any contributions for that issue. 🙂
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-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#23555
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?