[DOCS] {historic} file path bindings
Posted: 23 Mar 2022, 11:28
The {historic} dynamic binding will give you access to the original file path from the local rename history for the file at hand.
e.g. previous file path:
e.g. previous folder path:
e.g. previous file name:
e.g. you can use the {historic} binding in combination with --file-filter to select only files that have not yet been processed and thus don't yet have a record in the local rename history:
{historic.f} is particularly useful for -exec expressions that need to access the previous file path (as opposed to the new current file path) for newly processed files:
[DOCS] -exec custom post-process commands
e.g. previous file path:
Format: Select all
{ historic.f }e.g. previous folder path:
Format: Select all
{ historic.folder }e.g. previous file name:
Format: Select all
{ historic.fn }e.g. you can use the {historic} binding in combination with --file-filter to select only files that have not yet been processed and thus don't yet have a record in the local rename history:
Groovy: Select all
none{ historic }{historic.f} is particularly useful for -exec expressions that need to access the previous file path (as opposed to the new current file path) for newly processed files:
rednoah wrote: ↑14 Sep 2019, 19:43 e.g. call a custom script and pass along file paths and metadata:Shell: Select all
-exec /path/to/script.sh {f} {historic.f} {json}
[DOCS] -exec custom post-process commands