Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for broadcasting input to tabs, not just panes #16593

Open
Tracked by #16600
pabohoney1 opened this issue Jan 23, 2024 · 1 comment
Open
Tracked by #16600

Support for broadcasting input to tabs, not just panes #16593

pabohoney1 opened this issue Jan 23, 2024 · 1 comment
Labels
Area-Input Related to input processing (key presses, mouse, etc.) Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Product-Terminal The new Windows Terminal.
Milestone

Comments

@pabohoney1
Copy link

Description of the new feature/enhancement

I'd like a way to broadcast keyboard input to multiple tabs at once.

This has been asked for across multiple requests and they all get marked as a duplicate of #2634 but that only covers doing broadcasts in panes. This is a different request and I was unable to find an open issue for this. There are many examples of requests that are marked as duplicates of that but are asking for support for tabs, not panes.

Proposed technical implementation details (optional)

I don't have a preference for how this is done visually, just that I'm able to broadcast to multiple tabs via some mechanism. This can be via a new input window or (like iTerm2 does it) just sending exactly what I send in one tab to other tabs. Ideally there would be some options for choosing which tabs to which you're broadcasting.

@pabohoney1 pabohoney1 added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jan 23, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jan 23, 2024
@zadjii-msft
Copy link
Member

You know, this was originally discussed a bit in #9365, but we never really settled on a solution there. We should probably actually move that spec from being a draft to something finalized 😝

(we should probably file a "Broadcast Input follow-ups" megathread to track this in)

@carlos-zamora carlos-zamora added Product-Terminal The new Windows Terminal. Area-Input Related to input processing (key presses, mouse, etc.) and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jan 24, 2024
@carlos-zamora carlos-zamora added this to the Backlog milestone Jan 24, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Tag-Fix Doesn't match tag requirements label Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Input Related to input processing (key presses, mouse, etc.) Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Product-Terminal The new Windows Terminal.
Projects
None yet
Development

No branches or pull requests

3 participants