From a5ef7bc19bcd58a33bb385db729fd62c88e64b09 Mon Sep 17 00:00:00 2001
From: Ben Soares
{n}
, {++n}
, [*]
){n}
, {++n}
, [*]
, {m}
, {++m}
)
In the basic usage document we have a list of special strings that get replaced in output filename values with parts of input filename values.
@@ -97,8 +97,10 @@
because all of the command line arguments are read and sorted into their linked IDs before starting to be processed, and the [myId3]
specified linked ID takes precedence over the [*]
wildcard linked ID.
+ All of the substitutions talked about so far are evaluated in the argument parsing process. If in some cases (almost certainly involving structure images!) you find {n}
is not incrementing when you think it should, when specifying ‑‑structureimage
filenames you can also use {m}
and {++m}
, along with {structuredirname}
, {structurebasename}
and {structureextension}
which are substituted at the point of use. {m}
is just a plain counter starting at 0.
+