maintain own local copy of "release-groups.txt"

[Mothball1970]

I'll admit to not having waded through all 30 pages of this thread so apologies if this has been asked before, but has the topic of providing an option for users to maintain their own local copy of "release-groups.txt" been suggested? Such that if a local copy exists, use that; if no local copy exists, pull it from the github page.

In all reality, I probably will only ever hit maybe 15-20 group names that are on the list. But on the rare occasion I have a release from an unlisted group, it's usually a one-off or a group I've never seen before or since. Honestly, how many others have ever seen a release from RATTERA or KROKKERS? As such I do not want to submit it in a PR and wait for it to be approved for that group name to merely add more bloat to the 5325 names already on the list if it is rarely/never going to be used by me again or by anyone else. I'd rather open my locally saved copy of "release-groups.txt", append to it the new group name and in the stylizing I prefer, save it, then rename my files straight away.

If not, that's fine. I can manage well enough by tweaking { fn.match(/[-]([^-]+)$/) } to get what I need/want.

Thanks for all you do to make this a great program!

[rednoah]

I'd rather open my locally saved copy of "release-groups.txt", append to it the new group name and in the stylizing I prefer, save it, then rename my files straight away.

Yes, your custom format could do that. Check if file exists. Read lines. Check if {fn} matches anything. And so on. Read external CSV / TSV / JSON / XML files will get you started.

That said, you could just add your own checks in your custom format inline and leave it at that:

Format: Select all

{ any{ fn.match(/RATTERA|KROKKERS/) }{ group } }