All instances updated when settings.json changes? #12750

Closed
opened 2026-01-31 03:23:53 +00:00 by claunia · 1 comment
Owner

Originally created by @vefatica on GitHub (Feb 26, 2021).

I wanted a side-by-side comparison of Colsolas and Cascadia Code in two instances of WT and my default profile. With two instances running, both were updated when I saved the settings file (so I didn't get my comparison). Al running instances are updated regardless of which (if any) caused the settings file to be opened (including Settings UI). I'm not complaining but I was quite surprised. It's rather peculiar behavior. I can't think of another app that behaves that way.

Originally created by @vefatica on GitHub (Feb 26, 2021). I wanted a side-by-side comparison of Colsolas and Cascadia Code in two instances of WT and my default profile. With two instances running, both were updated when I saved the settings file (so I didn't get my comparison). Al running instances are updated regardless of which (if any) caused the settings file to be opened (including Settings UI). I'm not complaining but I was quite surprised. It's rather peculiar behavior. I can't think of another app that behaves that way.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 03:23:54 +00:00
Author
Owner

@DHowett commented on GitHub (Feb 26, 2021):

Yup! Terminal supports hot reloading when you edit the settings file. This is 100% by design and something we've spent a lot of time on getting right! 😄

@DHowett commented on GitHub (Feb 26, 2021): Yup! Terminal supports hot reloading when you edit the settings file. This is 100% by design and something we've spent a lot of time on getting right! :smile:
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12750