starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-09 02:26:45 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Support local profile settings (non-roaming) #2292

New Issue
Closed
opened 2026-01-30 22:51:41 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 22:51:41 +00:00
Owner
Copy Link

Originally created by @fpintos on GitHub (Jun 26, 2019).

Summary of the new feature/enhancement

Add support for two sets of profile settings:

  • (existing) roaming
  • (new) local, ie non-roaming

As it is today, Windows Terminal profile settings roam between machines, which can cause undesired profiles to show up in machines where their commands do not apply.

For example, I have a devbox and a laptop. I've created a command profile in my devbox that only apply to the devbox itself since it starts a particular batch file to configure the development environment; in my laptop I do not have the necessary files that are invoked by that profile. Yet, the profile replicated and shows up in the laptop.

Proposed technical implementation details (optional)

A solution for this might be to support different sets of profiles.
In addition to the roaming profile we could add support for a local profile.
Windows Terminal would then merge the two files at runtime.
With this, common commands, such as cmd/powershell/bash would live in the roaming file and machine-specific commands would live in the local file.

While at this, we might want to allow this local profile to live in a place easier to remember, like the user's home directory.

Originally created by @fpintos on GitHub (Jun 26, 2019). # Summary of the new feature/enhancement Add support for two sets of profile settings: - (existing) roaming - (new) local, ie non-roaming As it is today, Windows Terminal profile settings roam between machines, which can cause undesired profiles to show up in machines where their commands do not apply. For example, I have a devbox and a laptop. I've created a command profile in my devbox that only apply to the devbox itself since it starts a particular batch file to configure the development environment; in my laptop I do not have the necessary files that are invoked by that profile. Yet, the profile replicated and shows up in the laptop. # Proposed technical implementation details (optional) A solution for this might be to support different sets of profiles. In addition to the roaming profile we could add support for a local profile. Windows Terminal would then merge the two files at runtime. With this, common commands, such as cmd/powershell/bash would live in the roaming file and machine-specific commands would live in the local file. While at this, we might want to allow this local profile to live in a place easier to remember, like the user's home directory.
claunia commented 2026-01-30 22:51:42 +00:00
Author
Owner
Copy Link

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

We've got some settings changes in the works here, actually, as part of #754. Would you mind adding your request there? There's a specification in review at #1258 that will be setting our settings plan for the future.

@DHowett-MSFT commented on GitHub (Jun 27, 2019): We've got some settings changes in the works here, actually, as part of #754. Would you mind adding your request there? There's a specification in review at #1258 that will be setting our settings plan for the future.
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 Area-Settings Issue-Feature Needs-Tag-Fix Needs-Triage 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#2292
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?