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

Multi-cursor: Keyboard inputs across multiple panes #13560

New Issue
Closed
opened 2026-01-31 03:45:51 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 03:45:51 +00:00
Owner
Copy Link

Originally created by @dark-swordsman on GitHub (Apr 20, 2021).

Description of the new feature/enhancement

The ability to type into one pane and have that input sent to all panes, or to have the executed command on one pane be sent to all panes.

This feature exists on OSX's native terminal as multi-cursor, as well as in Mobaxterm as "Multi-exec". Though, the implementation on OSX allows you to toggle on or off with existing panes, where Mobaxterm requires you to re-configure the panes every time you open multi-execute.

An example of the benefit for this feature is if you are configuring two or more machines to do the same thing. It is useful when you are debugging and testing something, where a docker container or something similar may be too much effort for just testing.

So for example, say that I am running 6 VMs on a machine for game servers (let's say Counter Strike). It turns out that one or two lines in a configuration file need to be changed, and the changes would be done identically on all machines.

With multi-cursor, I would be able to make the change at the same time on all machines, save, and then reboot the VMs at the same time. This is in a scenario where docker containers are more effort than would be a benefit, especially when an image can be created locally on a VM host and spawned to other machines. But in this case, multi-cursor would come at a great benefit where time is sensitive.

As another note, I would add that you would be able to create multiple panes and then go to the same directory in each, though that matters more when each pane is on a different server. If on the same machine, then #3158 would basically solve that problem.

Originally created by @dark-swordsman on GitHub (Apr 20, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement The ability to type into one pane and have that input sent to all panes, or to have the executed command on one pane be sent to all panes. <!-- 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). --> This feature exists on OSX's native terminal as multi-cursor, as well as in Mobaxterm as "Multi-exec". Though, the implementation on OSX allows you to toggle on or off with existing panes, where Mobaxterm requires you to re-configure the panes every time you open multi-execute. An example of the benefit for this feature is if you are configuring two or more machines to do the same thing. It is useful when you are debugging and testing something, where a docker container or something similar may be too much effort for just testing. So for example, say that I am running 6 VMs on a machine for game servers (let's say Counter Strike). It turns out that one or two lines in a configuration file need to be changed, and the changes would be done identically on all machines. With multi-cursor, I would be able to make the change at the same time on all machines, save, and then reboot the VMs at the same time. This is in a scenario where docker containers are more effort than would be a benefit, especially when an image can be created locally on a VM host and spawned to other machines. But in this case, multi-cursor would come at a great benefit where time is sensitive. As another note, I would add that you would be able to create multiple panes and then go to the same directory in each, though that matters more when each pane is on a different server. If on the same machine, then #3158 would basically solve that problem.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 03:45:52 +00:00
claunia commented 2026-01-31 03:45:53 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 20, 2021):

Sounds like what you're describing is "Broadcast input mode", something we're tracking in #2634, that we've got a spec for in #9365, and we have a draft implementation in #9222.

/dup #2634

@zadjii-msft commented on GitHub (Apr 20, 2021): Sounds like what you're describing is "Broadcast input mode", something we're tracking in #2634, that we've got a spec for in #9365, and we have a draft implementation in #9222. /dup #2634
claunia commented 2026-01-31 03:45:53 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 20, 2021):

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 (Apr 20, 2021): 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!
claunia commented 2026-01-31 03:45:53 +00:00
Author
Owner
Copy Link

@iDevGIS commented on GitHub (Mar 27, 2024):

Yep!

@iDevGIS commented on GitHub (Mar 27, 2024): Yep!
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#13560
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?