[01:13:47] <@DES|GeneralDisarray> basically %whatever is just placeholders for whatever whitespace-delimited tokens happen to follow the command line
[01:13:56] <@DES|GeneralDisarray> follow the command name, sorry
[01:14:37] <@B}Ronald_Reagan> Why are they there then if the tokens are already there?
[01:21:07] <@DES|GeneralDisarray> can you give me an example of what you mean?
[01:23:28] <@B}Ronald_Reagan> Why do the numbers exist if you have your tokens there anyways. If you remove the tokens it would look more like something you would see on unix, however apparently you need them on windows?
[01:23:40] <@B}Ronald_Reagan> unix:
[01:24:20] <@B}Ronald_Reagan> bin_unix/ac_client --home="../../Data/settings" --init
[01:24:26] <@B}Ronald_Reagan> windows:
[01:24:35] <@B}Ronald_Reagan> bin_win32\ac_client.exe --home="..\..\Data\settings" --init %1 %2 %3 %4 %5
[01:24:47] <@B}Ronald_Reagan> I have a feeling I should just look up more about how windows reads .bat files
[01:25:11] <@DES|GeneralDisarray> indeed, %x is just a way of naming and passing (possible) parameters
[01:25:31] <@DES|GeneralDisarray> dunno about Unix so can't tell how they compare
[01:25:48] <@DES|GeneralDisarray> perhaps it's a given that parameters are passed on, so they're never specified
[01:25:51] <@B}Ronald_Reagan> so you need the %x to pass parameters.
[01:25:54] <@DES|GeneralDisarray> indeed
[01:25:59] <@B}Ronald_Reagan> ok
[01:26:00] <@DES|GeneralDisarray> else they're lost