Messages

Well, interaction with MC is needed in my example mentioned above. I have to run "git clone" from ${sourcepath}.

That's what I'm going to do now. So far it seemed to be pratical to have it all-in-one, as mentioned before...

For example navigating to a target directory and running "git clone", passing over the git repo path via the command line.

If command line arguments cannot be passed over I will have to seperate my batch scripts from Multicommander. So far, defining batch scripts inside Multicommander seemed to be a practical all-in-one solution for me, handling all the different types of user defined commands in a similar way.

I suggest to adapt the manual (http://multicommander.com/docs/UDC_batch, "Command Arguments").

Passing command arguments from the command line bar to a user defined batch script does not seem to work.
I wrote a small user defined batch script:

echo arg=${param:0}
pause

After assigning alias "ttt" to the batch script I entered "ttt 123" on the command line bar. Result:
arg=
Press any key ...

Can command line arguments only be passed to Multi-Scripts?