-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Feature Request - Add startup command for command line #933
Comments
Makes sense - I like it. It would be nice to be able to do more with mRemoteNG from the command line. Dev notes: |
If possible, can we add the startup commands as well to the connections, for example if i want to open logs for a group of connections, package them together and once opened its tailing the logs instead of writing it every time in multi SSH every time. |
Is there an update for this feature? |
I'd also be interested in having the possibility to start any existing connection from the CLI, either with started mRemoteNG or from a stopped state. |
what perhaps will be included into next release - idea to give user more flexibility with settings and atributes. |
Any updates? This feature would be awesome... |
I second this |
This feature would also be great for PAM solutions which automatically start RDP sessions. If we could start those RDP sessions into mremoteng |
Hi,
i'd like to be able to start mRemoteNG by command line with an argument to say "start the following connection directly at the startup".
I am using mRemote with integrated external application Cmder/ConEmu. It would be nice to run this directly when starting mRemote to have a suitable shell in front of the blank panel. Should look like the following:
How do you think about it?
kind regards, Mario
The text was updated successfully, but these errors were encountered: