You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 21, 2024. It is now read-only.
Now only slash is supported to pass parameters, but both slash and hyphen are filtered so you cant use them in your commands (for instance you can pass parameters to your remote command using slash).
I am sending a patch that makes remcom to only use slash for parameters and lets scape the first slash as 2 slash just in case you need to use slash as part of your remote command parameter.
So if you want to execute yourcommand.exe /aparameter you can do it with the following command RemCom.exe \remote "yourcommand.exe //aparameter"
Patch is on its way...
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We should both be more flexible, and allow less inconsistent/poor choices for parameter names.
E.g.
pwd
should bepassword
, orpass
, orp
. It should also support a hyphen instead of just a slash (not sure if it does now or not).Todo: Get some repro steps, and plan out the specific changes.
The text was updated successfully, but these errors were encountered: