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

Global configuration file #10946

New Issue
Closed
opened 2026-01-31 02:34:24 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 02:34:24 +00:00
Owner
Copy Link

Originally created by @OgreTransporter on GitHub (Oct 8, 2020).

Description of the new feature/enhancement

I would like there to be a global configuration file - e.g. in the program directory - where you can enter the available consoles for all users of a computer.

I have Anaconda, Python, Git-Bash, Gnuplot, GNU Octave, Lua and YACAS as consoles. It is annoying to have to re-enter the consoles for every new user on the computer.

Proposed technical implementation details (optional)

You can assign GUIDs, so that individual consoles can be deactivated if necessary via the local settings.json and the parameter hidden by the local user.

Originally created by @OgreTransporter on GitHub (Oct 8, 2020). # Description of the new feature/enhancement I would like there to be a global configuration file - e.g. in the program directory - where you can enter the available consoles for all users of a computer. I have Anaconda, Python, Git-Bash, Gnuplot, GNU Octave, Lua and YACAS as consoles. It is annoying to have to re-enter the consoles for every new user on the computer. # Proposed technical implementation details (optional) You can assign GUIDs, so that individual consoles can be deactivated if necessary via the local `settings.json` and the parameter `hidden` by the local user.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 02:34:24 +00:00
claunia commented 2026-01-31 02:34:25 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Oct 8, 2020):

Have a look at issue #2933. The general concept being proposed there is to have a way to import settings from another path. I think that probably covers what you're wanting to do.

@j4james commented on GitHub (Oct 8, 2020): Have a look at issue #2933. The general concept being proposed there is to have a way to import settings from another path. I think that probably covers what you're wanting to do.
claunia commented 2026-01-31 02:34:25 +00:00
Author
Owner
Copy Link

@OgreTransporter commented on GitHub (Oct 8, 2020):

The discussion is interesting. But I don't want to use one settings.json for all users. I want a global configuration file for all users with some basic settings. If a user does not like the color he can overwrite it in his local configuration file.

@OgreTransporter commented on GitHub (Oct 8, 2020): The discussion is interesting. But I don't want to use one settings.json for all users. I want a global configuration file for all users with some basic settings. If a user does not like the color he can overwrite it in his local configuration file.
claunia commented 2026-01-31 02:34:25 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Oct 8, 2020):

The solution proposed in that issue was the ability to import settings from other files. See the comment here: https://github.com/microsoft/terminal/issues/2933#issuecomment-536652883

Given that functionality, each user could have their own settings file with their local overrides, and then some kind of import directive that linked in the shared configuration from a global settings file. Is that not what you want?

@j4james commented on GitHub (Oct 8, 2020): The solution proposed in that issue was the ability to import settings from other files. See the comment here: https://github.com/microsoft/terminal/issues/2933#issuecomment-536652883 Given that functionality, each user could have their own settings file with their local overrides, and then some kind of import directive that linked in the shared configuration from a global settings file. Is that not what you want?
claunia commented 2026-01-31 02:34:25 +00:00
Author
Owner
Copy Link

@PankajBhojwani commented on GitHub (Oct 8, 2020):

This is very much on our roadmap! #7584 /#7632 outline the initial work needed and this will come at some point after

@PankajBhojwani commented on GitHub (Oct 8, 2020): This is very much on our roadmap! #7584 /#7632 outline the initial work needed and this will come at some point after
claunia commented 2026-01-31 02:34:25 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 15, 2020):

Interesting. You raise an good idea about the ordering mattering here. We'll want to make sure that the user can have files that they import before loading their settings file, and other settings that they load after.

"Proto extensions" might be the easiest solution here. With that, you'll be able to drop a fragment of profiles & settings into a global install location, and then all users should be able to have that fragment of settings applied before their own settings.json. I'm going to call this a dupe, even if it's not exactly the same thing, you should be able to get the same effect.

/dup #7632

@zadjii-msft commented on GitHub (Oct 15, 2020): Interesting. You raise an good idea about the ordering mattering here. We'll want to make sure that the user can have files that they import _before_ loading their settings file, and other settings that they load _after_. "Proto extensions" might be the easiest solution here. With that, you'll be able to drop a fragment of profiles & settings into a global install location, and then all users should be able to have that fragment of settings applied before their own `settings.json`. I'm going to call this a dupe, even if it's not _exactly_ the same thing, you should be able to get the same effect. /dup #7632
claunia commented 2026-01-31 02:34:25 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 15, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Oct 15, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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#10946
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?