mutually independent custom criteria / support for logical operators like OR

[LnLcFlx]

I want to stack images according to two different criteria indepentdently

1. I want to stack images with in the same directory that match some originalFileName criterion
2. I want to stack images with the same time and this originalFileName criterion

Let's say I have images

1. /foo/img1.jpg
2. /foo/img1_edit.jpg
3. /foo/img2.jpg
4. /bar/img2.jpg
5. /bar/img2_edit.jpg
   where img1.jpg, img1_edit.jpg may have different timestamps and all img2* have the same timestamp.

Criterion 1 would stack images (1,2) and (4,5), because they are in the same directory as their stack siblings and their file name regex capture img1/img2 matches, even thought their timestamp might not.

Criterion 2 would stack images (3,4) because their filenames match and their timestamps do too, even though their directories don't.

What I want is both, i.e. the final stacks (1,2) and (3,4,5).

AFAIK, I could achive this right now by running the script twice, once with criterion 1 and after that with 2 (I think it will work because by default stacks won't be unstacked but just extended if already stacked).

This is of course a little ugly and might not work reliably when ran automatically in cron mode.

It would thus be great to supply multiple sets of independent criteria.
This, however, poses additional questions:

1. Whereas the current behavior links criteria via a logical AND, i.e. all criteria have to be fulfilled, these independent sets of criteria would correspond to an OR operation.
   Maybe it would be better for more sophisticated stacking tasks to implement a full logic parsing?
2. At the latest at this point, I think the env var is starting to get very long and being able to supply a config file would be great.
   At least being able to supply the custom criteria on a JSON file would be nice.

These points unregarded, the simplest implementation of my original idea would be to add another layer of JSON nesting, where the outer most list is, as currently, the "AND list".
This"AND list" contains either criteria (ducts) themselves, like right now, or other lists which are then "OR lists".
Or the vice versa (?)

But you see, this is getting ugly...
So my third proposal is:
Would it be more viable to plug-in criteria via golang directly?
I don't know any go, but maybe something like supplying a go config where if a certain function is supplied it used as the criterion logic.

[Majorfi]

#33 will be merged this week and should provide a way to exclude images

[LnLcFlx]

Great work, thank you!