Multi-panel execution mode - Focus multiple panels at a time #14510

Closed
opened 2026-01-31 04:12:13 +00:00 by claunia · 2 comments
Owner

Originally created by @c0depool on GitHub (Jul 14, 2021).

Description of the new feature/enhancement

It would be nice to have a feature to write on to multi-panels - where the user can simultaneously write to all panels at the same time. Useful while working with multiple machines which have the same setup on scenarios like checking logs, listing files etc. MobaXterm is already having such a feature. Currently on wt when working with multiple panels, we can only focus on a single panel at a time.

Originally created by @c0depool on GitHub (Jul 14, 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 It would be nice to have a feature to write on to multi-panels - where the user can simultaneously write to all panels at the same time. Useful while working with multiple machines which have the same setup on scenarios like checking logs, listing files etc. MobaXterm is already having such a feature. Currently on wt when working with multiple panels, we can only focus on a single panel at a time. <!-- 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). --> <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 04:12:13 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Jul 14, 2021):

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #2634 for more discussion.

/dup #2634

@zadjii-msft commented on GitHub (Jul 14, 2021): Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #2634 for more discussion. /dup #2634
Author
Owner

@ghost commented on GitHub (Jul 14, 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 (Jul 14, 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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#14510