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

Provide manual refresh of settings.json or have refresh code follow symlinks #8607

New Issue
Open
opened 2026-01-31 01:33:40 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 01:33:40 +00:00
Owner
Copy Link

Originally created by @brianpepin on GitHub (May 26, 2020).

Provide a way to manually refresh Terminal's reading of settings.json or have the update sniff follow symbolic links.

I like to keep important state for my dev machine in a git repo so I can blow away the machine and easily recreate it if I need to. I have settings.json living in this repo and I've created a symbolic link at the original location. This all works fine. But now if I change settings I need to close reopen terminal windows -- the changes are not automatically updated. It would be great if there was a way to trigger a re-parse of settings, or have Terminal follow symbolic links and monitor their targets for changes (I couldn't use a hard link -- different drives).

Proposed technical implementation details (optional)

Ideally the file change monitor for settings would detect if settings is using a symlink and monitor the target. Less ideally, but probably useful in more situations is to have an option to reload settings manually.

Originally created by @brianpepin on GitHub (May 26, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> Provide a way to manually refresh Terminal's reading of settings.json or have the update sniff follow symbolic links. I like to keep important state for my dev machine in a git repo so I can blow away the machine and easily recreate it if I need to. I have settings.json living in this repo and I've created a symbolic link at the original location. This all works fine. But now if I change settings I need to close reopen terminal windows -- the changes are not automatically updated. It would be great if there was a way to trigger a re-parse of settings, or have Terminal follow symbolic links and monitor their targets for changes (I couldn't use a hard link -- different drives). # Proposed technical implementation details (optional) Ideally the file change monitor for settings would detect if settings is using a symlink and monitor the target. Less ideally, but probably useful in more situations is to have an option to reload settings manually.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 01:33:40 +00:00
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#8607
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?