Suggestion: Add an "OR" operator to FIELDS input of actions

[ohrenkino]

@jackpots

It is my impression that to apply a set of rules in actions to more than one tag field, one has to create multiply actions sets or use _TAG. However and often, _TAG is too indiscriminate and affects tags that should be not changed.

Scenario:
You have a series of 10+ rules to apply to ARTIST but want to apply the identical set to ALBUMARTIST, TITLE, COMPOSER, BAND, COMPOSER, LYRICIST and their ~SORTs but not touch all other tag fields.

Instead of…
[#13]
T=4
F=ARTIST
1=(^\\s+|\\s+$)
2=
3=0

Their would be…
[#13]
T=4
F=ARTIST|ARTISTSORT|TITLE|TITLESORT|…
1=(^\\s+|\\s+$)
2=
3=0

Thanks.

I think that the example you gave could be dealt with the idea given in this thread:
/t/9138/1

Other than this concrete application of trimming I can hardly think of actions that deal with so many fields or have to be limited to a set of fields (e.g. replacing Umlauts and things).
The trimming probably does not work on filenames if you have composed the old filename with bits and pieces from now trimmed fields. The additional spaces will probably remain inside the string.