First of all, thanks a lot for these scripts! It's the best and greatest collection I have seen so far.
One thought from my side on this rule:
output ≠ input, never erase input!
Currently, this increases the number of steps in my workflow significantly. I do not only have to apply the script, but also have to remove the input files afterwards and remove the suffixes of the output files, as I want to keep my folders clean and not too bloated.
I guess the rule aims at easily recovering old files when a script somehow damages it? Could it be an option to trash the input file (making it thereby recoverable via the common system trash function) and write an output with the name of the input? I'm not sure how much work this would be, but even if you're not convinced this should be the default behavior, you could maybe add it as an option at the beginning of the scripts?
First of all, thanks a lot for these scripts! It's the best and greatest collection I have seen so far.
One thought from my side on this rule:
Currently, this increases the number of steps in my workflow significantly. I do not only have to apply the script, but also have to remove the input files afterwards and remove the suffixes of the output files, as I want to keep my folders clean and not too bloated. I guess the rule aims at easily recovering old files when a script somehow damages it? Could it be an option to trash the input file (making it thereby recoverable via the common system trash function) and write an output with the name of the input? I'm not sure how much work this would be, but even if you're not convinced this should be the default behavior, you could maybe add it as an option at the beginning of the scripts?