Skip to content

Multi-cursor: Keyboard inputs across multiple panes #9899

Closed

Description

@dark-swordsman

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.

Activity

  1. added
    Issue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.
    on Apr 19, 2021
  2. ghost added
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Apr 19, 2021
  3. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on Apr 19, 2021
  4. zadjii-msft commented on Apr 20, 2021

    @zadjii-msft
    Member

    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

  5. ghost closed this as completedon Apr 20, 2021
  6. ghost removed
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Apr 20, 2021
  7. ghost added
    Resolution-DuplicateThere's another issue on the tracker that's pretty much the same thing.
    on Apr 20, 2021
  8. ghost removed
    Needs-Tag-FixDoesn't match tag requirements
    on Apr 20, 2021
  9. iDevGIS commented on Mar 27, 2024

    @iDevGIS

    Yep!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.Resolution-DuplicateThere's another issue on the tracker that's pretty much the same thing.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions