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

Add support for sending keystrokes or commands to multiple panes #7932

Closed
Riari opened this issue Oct 15, 2020 · 3 comments
Closed

Add support for sending keystrokes or commands to multiple panes #7932

Riari opened this issue Oct 15, 2020 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@Riari
Copy link

Riari commented Oct 15, 2020

Edit: Apologies for the duplicate; I did search before but missed the other issues, I think because of differences in phrasing/describing the feature.

Description of the new feature/enhancement

With the current implementation of panes, it's not possible to send keystrokes or commands to multiple panes at once; you have to navigate to each pane to interact with them one by one. It would be nice if we could do one of the following:

A) Send keys to specific panes (a la tmux's send-keys)
B) Focus multiple panes at once in order to interact with them simultaneously
C) Open a text input via a new keyboard shortcut to enter text and hit enter to send it to all panes in the current tab

B or C would be preferable for my use cases (e.g. checking out a specific branch across multiple git repos), but I think any of these would be a welcome addition.

@Riari Riari added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Oct 15, 2020
@ghost ghost added 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 Oct 15, 2020
@Don-Vito
Copy link
Contributor

Seems to duplicate #2634

@zadjii-msft
Copy link
Member

Yep, this is definitely /dup #2634. Was there a twitter thread about this recently or something? #7919 was also just recently filed about this same thing 🤔

@ghost
Copy link

ghost commented Oct 15, 2020

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 ghost closed this as completed Oct 15, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. 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 Oct 15, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants