mRemoteNG / mRemoteNG/mRemoteNG
Add support for excluding certain active connections from multi ssh commands
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 11.1k
- Forks
- 1.6k
- Avg merge
- 16h 58m
- Merged PRs (30d)
- 55
Description
Original Description:
Requesting feature to disable/enable accepting commands for "Multi ssh"
Merging request from #1100:
Send command using the MultiSSH toolbar only to the SSH connection inside the currently focused Connection Panel. Preferably optional by checkbox.
Expected Behavior
It would be nice if there would be an option to limit the command forwarding only to the SSH connections, which are in the currently focused Connection Panel.
Current Behavior
Currently the MultiSSH toolbar will send the command to all open SSH connections, independent of the Connection Panel.
Possible Solution
Add checkbox to the MultiSSH toolbar to limit command forwarding only to the SSH connection in the current Connection Panel.
Context
We have SSH connections to different Docker machines. It would save time to have all connections open but to organize them into Connection Panels and to send commands based on the panels.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the MultiSSH toolbar's command-forwarding path and how the currently focused Connection Panel is identified. Add an optional setting that limits forwarding to SSH connections in that panel, and verify that the default behavior still sends commands to all open SSH connections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100