Feature Request - use a directory for profiles #3216

Open
opened 2026-01-30 23:16:02 +00:00 by claunia · 0 comments
Owner

Originally created by @dbacher on GitHub (Aug 6, 2019).

Use C:\ProgramData\Microsoft\Terminal, or similar, make a directory named "Profiles."
Use %APPDATA%\Microsoft\Terminal, or similar, make a directory there named "Profiles."

On startup, while reading the settings - enumerate each file in those two directories (maybe with a JSON file extension), parse it, and if it parses - add it to the profiles.

That would allow an installer from another team, for example from Visual Studio, Azure, etc. to hang a profile just by copying in a file like visual-studio-2019-cmd-tools.json or windows-platform-sdk.json.

Using separate files makes uninstall better, but this would basically be very similar to /etc/shells on Linux.

Originally created by @dbacher on GitHub (Aug 6, 2019). Use C:\ProgramData\Microsoft\Terminal, or similar, make a directory named "Profiles." Use %APPDATA%\Microsoft\Terminal, or similar, make a directory there named "Profiles." On startup, while reading the settings - enumerate each file in those two directories (maybe with a JSON file extension), parse it, and if it parses - add it to the profiles. That would allow an installer from another team, for example from Visual Studio, Azure, etc. to hang a profile just by copying in a file like visual-studio-2019-cmd-tools.json or windows-platform-sdk.json. Using separate files makes uninstall better, but this would basically be very similar to /etc/shells on Linux.
claunia added the Issue-FeatureArea-SettingsNeeds-Tag-FixProduct-Terminal labels 2026-01-30 23:16:03 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#3216