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

Feature Request: Option to change location of profiles.json #1958

New Issue
Closed
opened 2026-01-30 22:42:49 +00:00 by claunia · 9 comments
claunia commented 2026-01-30 22:42:49 +00:00
Owner
Copy Link

Originally created by @logonoff on GitHub (Jun 23, 2019).

Summary of the new feature/enhancement

Going though local appdata is hard and it'd be nice if you could change where it fetches the config file. a usecase could be people who have dotfiles repos to place their config in the user dir or config folder instead of making a symlink

Proposed technical implementation details (optional)

Maybe put the path of it in a json file and have it configurable via a gui?

Originally created by @logonoff on GitHub (Jun 23, 2019). # Summary of the new feature/enhancement Going though local appdata is hard and it'd be nice if you could change where it fetches the config file. a usecase could be people who have dotfiles repos to place their config in the user dir or config folder instead of making a symlink <!-- 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). --> # Proposed technical implementation details (optional) Maybe put the path of it in a json file and have it configurable via a gui? <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureArea-SettingsProduct-TerminalResolution-Won't-Fix labels 2026-01-30 22:42:49 +00:00
claunia commented 2026-01-30 22:42:50 +00:00
Author
Owner
Copy Link

@fredrikaverpil commented on GitHub (Jun 24, 2019):

I would like to symlink ~\dotfiles\profiles.json to ~\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState\profiles.json but I am curious about that 8wekyb3d8bbwe identifier in the path.

What is it for and will it change?

@fredrikaverpil commented on GitHub (Jun 24, 2019): I would like to symlink `~\dotfiles\profiles.json` to `~\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState\profiles.json` but I am curious about that `8wekyb3d8bbwe` identifier in the path. What is it for and will it change?
claunia commented 2026-01-30 22:42:50 +00:00
Author
Owner
Copy Link

@kumarharsh commented on GitHub (Jun 26, 2019):

I think 8wekyb3d8bbwe identifier is a fixed string (perhaps related to it's Store ID or something similar), and won't change.

@kumarharsh commented on GitHub (Jun 26, 2019): I think `8wekyb3d8bbwe` identifier is a fixed string (perhaps related to it's Store ID or something similar), and won't change.
claunia commented 2026-01-30 22:42:50 +00:00
Author
Owner
Copy Link

@Cologler commented on GitHub (Jun 26, 2019):

I guess 8wekyb3d8bbwe is the store publisher id of Microsoft.

@Cologler commented on GitHub (Jun 26, 2019): I guess 8wekyb3d8bbwe is the store publisher id of Microsoft.
claunia commented 2026-01-30 22:42:51 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 27, 2019):

We're probably not going to do this. A symbolic link will work. The identity, 8wek..., is based on the name used to sign the app bundle. This one means "Microsoft." It won't change.

@DHowett-MSFT commented on GitHub (Jun 27, 2019): We're probably not going to do this. A symbolic link will work. The identity, `8wek...`, is based on the name used to sign the app bundle. This one means "Microsoft." It won't change.
claunia commented 2026-01-30 22:42:51 +00:00
Author
Owner
Copy Link

@franjozen commented on GitHub (Aug 14, 2019):

The problem with a symbolic link is that the terminal doesn't react to the settings changing.

@franjozen commented on GitHub (Aug 14, 2019): The problem with a symbolic link is that the terminal doesn't react to the settings changing.
claunia commented 2026-01-30 22:42:51 +00:00
Author
Owner
Copy Link

@fredrikaverpil commented on GitHub (Aug 14, 2019):

@franjozen are you sure?
I am 90% sure my terminal reacts to changes immediately when editing the profile and I have a symlink set up to my dotfiles. I can check once I am at my computer.

@fredrikaverpil commented on GitHub (Aug 14, 2019): @franjozen are you sure? I am 90% sure my terminal reacts to changes immediately when editing the profile and I have a symlink set up to my dotfiles. I can check once I am at my computer.
claunia commented 2026-01-30 22:42:51 +00:00
Author
Owner
Copy Link

@franjozen commented on GitHub (Aug 16, 2019):

@fredrikaverpil Yes, I've created the symlink like this:
new-item -itemtype symboliclink -path .\ -name profiles.json -value ..\..\..\..\..\dotfiles\WindowsTerminal\profiles.json
Nothing happens when I save, I have to restart Terminal to see the changes.

@franjozen commented on GitHub (Aug 16, 2019): @fredrikaverpil Yes, I've created the symlink like this: `new-item -itemtype symboliclink -path .\ -name profiles.json -value ..\..\..\..\..\dotfiles\WindowsTerminal\profiles.json` Nothing happens when I save, I have to restart Terminal to see the changes.
claunia commented 2026-01-30 22:42:51 +00:00
Author
Owner
Copy Link

@fredrikaverpil commented on GitHub (Aug 16, 2019):

@franjozen oh, it seems I have the very same behavior here as on your end.

@fredrikaverpil commented on GitHub (Aug 16, 2019): @franjozen oh, it seems I have the very same behavior here as on your end.
claunia commented 2026-01-30 22:42:51 +00:00
Author
Owner
Copy Link

@Antorell commented on GitHub (Sep 12, 2020):

Sorry for bumping this closed post. Posting if somebody hasn't figured yet.
You need to create a junction/SymbolicLink to the LocalState folder that link to a folder that contains the WT settings.json instead of linking the settings.json directly, if you want the settings to update right away when you edit the settings.json.

Something like this:
New-Item -Force -Type Junction -Path "$ENV:LOCALAPPDATA\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState" -Value "Path\to\myfolder\withtheWTsettings.json\insideit"

@Antorell commented on GitHub (Sep 12, 2020): Sorry for bumping this closed post. Posting if somebody hasn't figured yet. You need to create a junction/SymbolicLink to the LocalState folder that link to a folder that contains the WT settings.json instead of linking the settings.json directly, if you want the settings to update right away when you edit the settings.json. Something like this: New-Item -Force -Type Junction -Path "$ENV:LOCALAPPDATA\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState" -Value "Path\to\myfolder\withtheWTsettings.json\insideit"
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 Area-Settings Issue-Feature Product-Terminal Resolution-Won't-Fix
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#1958
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?