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

Opening a New Pane with "-" or "+" Opens the First Profile, Regardless of Current Profile #10657

New Issue
Closed
opened 2026-01-31 02:26:45 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 02:26:45 +00:00
Owner
Copy Link

Originally created by @parasnailor on GitHub (Sep 17, 2020).

Originally assigned to: @zadjii-msft on GitHub.

Description

When opening a new split pane with alt+shift+d, the new pane will be of the same terminal profile as the pane from which it was spawned. However, when specifying a vertical or horizontal split pane with alt+shift+plus or alt+shift+minus, the new pane is always of the first terminal profile listed under "profiles" in "settings.json."
This is undesirable for two reasons:

  1. It can result in terminal tabs of mixed profiles. In my use case, it results in a terminal tab running the Powershell profile, with a split pane running the Ubuntu WSL profile. It's possible that this is intended behavior, but I found it confusing.
  2. There is currently no way (that I know of) to open a new split pane and specify a vertical or horizontal split for any profile except for the first one. Attempting to specify a vertical or horizontal split for any profile other than the first always results in a split pane running the first profile.

Expected Behavior

I would expect that behavior (in terms of which profile is used for the pane) would at least be consistent between alt+shift+d and alt+shift+minus/plus. Optimally, I would expect that all three shortcuts would always spawn a new split pane of the same profile that was active when the shortcut was entered.

Originally created by @parasnailor on GitHub (Sep 17, 2020). Originally assigned to: @zadjii-msft on GitHub. Description ----------- When opening a new split pane with `alt+shift+d`, the new pane will be of the same terminal profile as the pane from which it was spawned. However, when specifying a vertical or horizontal split pane with `alt+shift+plus` or `alt+shift+minus`, the new pane is always of the first terminal profile listed under "profiles" in "settings.json." This is undesirable for two reasons: 1. It can result in terminal tabs of mixed profiles. In my use case, it results in a terminal tab running the Powershell profile, with a split pane running the Ubuntu WSL profile. It's possible that this is intended behavior, but I found it confusing. 2. There is currently no way (that I know of) to open a new split pane and specify a vertical or horizontal split for any profile except for the first one. Attempting to specify a vertical or horizontal split for any profile other than the first always results in a split pane running the first profile. Expected Behavior ------------------ I would expect that behavior (in terms of which profile is used for the pane) would at least be consistent between `alt+shift+d` and `alt+shift+minus/plus.` Optimally, I would expect that all three shortcuts would always spawn a new split pane of the same profile that was active when the shortcut was entered.
claunia commented 2026-01-31 02:26:46 +00:00
Author
Owner
Copy Link

@parasnailor commented on GitHub (Sep 17, 2020):

Windows Terminal Issue

Attached is an image of a terminal tab running Powershell (my # 2 profile) in the left (original) pane. alt+shift+d was used to open the pane in the top right, which is (correctly) running Powershell. alt+shift+minus was used from the top right pane to open the bottom right pane, which is (incorrectly) running WSL Ubuntu, my # 1 profile. Note the different theme, as well as the tab title changing to that of my Ubuntu WSL profile.

@parasnailor commented on GitHub (Sep 17, 2020): ![Windows Terminal Issue](https://user-images.githubusercontent.com/30733734/93524897-31909b00-f903-11ea-9bb4-9c3f04ee7d48.png) Attached is an image of a terminal tab running Powershell (my # 2 profile) in the left (original) pane. `alt+shift+d` was used to open the pane in the top right, which is (correctly) running Powershell. `alt+shift+minus` was used from the top right pane to open the bottom right pane, which is (incorrectly) running WSL Ubuntu, my # 1 profile. Note the different theme, as well as the tab title changing to that of my Ubuntu WSL profile.
claunia commented 2026-01-31 02:26:46 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 18, 2020):

So, we've heard this issue time and time again and we've always closed it and said "you can set these bindings up yourself; just add "split": "duplicate" to your version of the split pane bindings". I'm no longer convinced that our default behavior should be so... weird.

If a bunch of users are asking for it, and telling us that Terminal's done something unexpected, we should probably do the "expected" thing.

@cinnamon-msft, @zadjii-msft: I propose that we make the split pane bindings duplicate by default.

@DHowett commented on GitHub (Sep 18, 2020): So, we've heard this issue time and time again and we've always closed it and said "you can set these bindings up yourself; just add `"split": "duplicate"` to your version of the split pane bindings". I'm no longer convinced that our default behavior should be so... weird. If a bunch of users are asking for it, and telling us that Terminal's done something unexpected, we should probably do the "expected" thing. @cinnamon-msft, @zadjii-msft: I propose that we make the split pane bindings _duplicate by default_.
claunia commented 2026-01-31 02:26:46 +00:00
Author
Owner
Copy Link

@cinnamon-msft commented on GitHub (Sep 18, 2020):

I'm down for this. 👍

@cinnamon-msft commented on GitHub (Sep 18, 2020): I'm down for this. 👍
claunia commented 2026-01-31 02:26:46 +00:00
Author
Owner
Copy Link

@rostidev commented on GitHub (Sep 28, 2020):

I faced this problem too and almost started to write a new bug report.
I see two ways of fixing it:

  1. Add "splitMode": "duplicate" into the default bindings of alt+shift+plus and alt+shift+minus, as already mentioned above. But users who are good with current key bindings of split pane may not like this change.
  2. Add following two new bindings by default: 
    { "command": { "action": "splitPane", "split": "horizontal", "splitMode": "duplicate"}, "keys": "alt+shift+numpad_minus" },
{ "command": { "action": "splitPane", "split": "vertical", "splitMode": "duplicate"}, "keys": "alt+shift+numpad_plus" }
    With those new bindings, when you split, for example, a pane of an SSH profile you may choose between opening a new SSH session into the same remote machine or the default profile that's usually a local CMD or Powershell. Also it doesn't change an existing behavior and users that are good with the current default bindings of split pane will not complain.

@DHowett

So, we've heard this issue time and time again and we've always closed it and said "you can set these bindings up yourself; just add "split": "duplicate" to your version of the split pane bindings".

Please don't close without fixing.

@rostidev commented on GitHub (Sep 28, 2020): I faced this problem too and almost started to write a new bug report. I see two ways of fixing it: 1. Add `"splitMode": "duplicate"` into the default bindings of `alt+shift+plus` and `alt+shift+minus`, as already mentioned above. But users who are good with current key bindings of split pane may not like this change. 2. Add following two new bindings by default: ``` { "command": { "action": "splitPane", "split": "horizontal", "splitMode": "duplicate"}, "keys": "alt+shift+numpad_minus" }, { "command": { "action": "splitPane", "split": "vertical", "splitMode": "duplicate"}, "keys": "alt+shift+numpad_plus" } ``` With those new bindings, when you split, for example, a pane of an SSH profile you may choose between opening a new SSH session into the same remote machine or the default profile that's usually a local CMD or Powershell. Also it doesn't change an existing behavior and users that are good with the current default bindings of split pane will not complain. @DHowett > So, we've heard this issue time and time again and we've always closed it and said "you can set these bindings up yourself; just add "split": "duplicate" to your version of the split pane bindings". Please don't close without fixing.
claunia commented 2026-01-31 02:26:46 +00:00
Author
Owner
Copy Link

@Don-Vito commented on GitHub (Feb 7, 2021):

If Kayla agreed, any reason we do not enable it by default?

@Don-Vito commented on GitHub (Feb 7, 2021): If Kayla agreed, any reason we do not enable it by default?
claunia commented 2026-01-31 02:26:47 +00:00
Author
Owner
Copy Link

@awa5114 commented on GitHub (Jan 29, 2022):

I'm also of the opinion that this behavior should occur by default. Seems counterintuitive that splitting panes results in a new profile.

@awa5114 commented on GitHub (Jan 29, 2022): I'm also of the opinion that this behavior should occur by default. Seems counterintuitive that splitting panes results in a new profile.
claunia commented 2026-01-31 02:26:47 +00:00
Author
Owner
Copy Link

@leet0rz commented on GitHub (Jun 15, 2022):

Yeah, this should be default and is still an issue, it is still not duplicate of original shell you've opened by default when opening new split it opens the "first profile" and not the one you are working with.

@leet0rz commented on GitHub (Jun 15, 2022): Yeah, this should be default and is still an issue, it is still not duplicate of original shell you've opened by default when opening new split it opens the "first profile" and not the one you are working with.
claunia commented 2026-01-31 02:26:47 +00:00
Author
Owner
Copy Link

@dovholuknf commented on GitHub (May 26, 2023):

I'd just like to be able to split a pane and choose the profile even if i had to do it with my mouse. I still figure out how to do that. I've just resorted to using bash for everything and then immediately running cmd.exe or pwsh.exe as i need to but that's a bummer...

I'd really appreciate a key to add to let me pick whatever profile i want... like when i do "shift-alt-minus" the default profile is used, cool but if I do "shift-ctrl-alt-minus" then i get to pick what profile to use

@dovholuknf commented on GitHub (May 26, 2023): I'd just like to be able to split a pane and choose the profile even if i had to do it with my mouse. I still figure out how to do that. I've just resorted to using bash for everything and then immediately running cmd.exe or pwsh.exe as i need to but that's a bummer... I'd really appreciate a key to add to let me pick whatever profile i want... like when i do "shift-alt-minus" the default profile is used, cool but if I do "shift-ctrl-alt-minus" then i get to pick what profile to use
claunia commented 2026-01-31 02:26:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 2, 2023):

Looping back on this after years: team consensus is that this is a good idea and we're gonna do this for 1.20. As well as include the old JSON in the patch notes, for users who want to go back. Thanks for the patience folks ☺️

@zadjii-msft commented on GitHub (Oct 2, 2023): Looping back on this after _years_: team consensus is that this is a good idea and we're gonna do this for 1.20. As well as include the old JSON in the patch notes, for users who want to go back. Thanks for the patience folks ☺️
claunia commented 2026-01-31 02:26:48 +00:00
Author
Owner
Copy Link

@parasnailor commented on GitHub (Oct 5, 2023):

Looping back on this after years: team consensus is that this is a good idea and we're gonna do this for 1.20. As well as include the old JSON in the patch notes, for users who want to go back. Thanks for the patience folks ☺️

The system works!

@parasnailor commented on GitHub (Oct 5, 2023): > Looping back on this after _years_: team consensus is that this is a good idea and we're gonna do this for 1.20. As well as include the old JSON in the patch notes, for users who want to go back. Thanks for the patience folks ☺️ The system works!
claunia commented 2026-01-31 02:26:48 +00:00
Author
Owner
Copy Link

@b-hayes commented on GitHub (May 21, 2024):

I see no reason to be willfully ignorant of the users' context by default. I would have filed a bug for this behaviour too if I didn't see this.

@b-hayes commented on GitHub (May 21, 2024): I see no reason to be willfully ignorant of the users' context by default. I would have filed a bug for this behaviour too if I didn't see this.
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 Help Wanted In-PR Issue-Task Needs-Tag-Fix Product-Terminal
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#10657
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?