[Feature Request] Global settings to overwrite per-profile ones #1948

Closed
opened 2026-01-30 22:42:40 +00:00 by claunia · 5 comments
Owner

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

Summary of the new feature/enhancement

I would love to be able to overwrite per profile settings with a global one, let's say I want to use the same color scheme everywhere, setting it in the global section should do that.

Proposed technical implementation details (optional)

Originally created by @Stanzilla on GitHub (Jun 23, 2019). # Summary of the new feature/enhancement <!-- 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). --> I would love to be able to overwrite per profile settings with a global one, let's say I want to use the same color scheme everywhere, setting it in the global section should do that. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureNeeds-Tag-FixResolution-DuplicateProduct-Terminal labels 2026-01-30 22:42:40 +00:00
Author
Owner

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

Absolutely do. #754 partially covers this, and is in spec review. Would you be willing to chip in your support over there?

@DHowett-MSFT commented on GitHub (Jun 23, 2019): Absolutely do. #754 partially covers this, and is in spec review. Would you be willing to chip in your support over there?
Author
Owner

@Stanzilla commented on GitHub (Jun 23, 2019):

Done!

@Stanzilla commented on GitHub (Jun 23, 2019): Done!
Author
Owner

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

This issue has been marked as duplicate and has not had any activity for 1 day. It will be closed for housekeeping purposes.

@ghost commented on GitHub (Jun 24, 2019): This issue has been marked as duplicate and has not had any activity for **1 day**. It will be closed for housekeeping purposes.
Author
Owner

@Stanzilla commented on GitHub (Jul 26, 2019):

@DHowett can we un-dupe this? I don't think it's really what #754 is about.

@Stanzilla commented on GitHub (Jul 26, 2019): @DHowett can we un-dupe this? I don't think it's really what #754 is about.
Author
Owner

@DHowett-MSFT commented on GitHub (Jul 26, 2019):

It is; we're still mulling over what goes into the spec, but there's a contingent of us in here saying that it should include an affordance for this.
Really, it would go the opposite way from how it's been suggested here. Baseline profiles would be loaded, global user defaults would be applied, and then profile-specific user configurations would be overlaid. The "most specific" category should always win.

@DHowett-MSFT commented on GitHub (Jul 26, 2019): It is; we're still mulling over what goes into the spec, but there's a contingent of us in here saying that it should include an affordance for this. Really, it would go the opposite way from how it's been suggested here. Baseline profiles would be loaded, global user defaults would be applied, and then profile-specific user configurations would be overlaid. The "most specific" category should always win.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1948