What's the difference between this and random_exclude_pattern?

The result of this exclusion is that certain paths/files that comes from mpd will not show up in search and add-random. But they are still browseable. I admit the use-case might be very particular to myself... I have a symlink tree for sorting songs i various ways, but don't want duplicates when searching.

Have rebased this now!

Rebased again

I know it's been ages, but since you rebased recently I guess you keep using it.

1. The "Exclude pattern for whole database" is misleading, because it's not considered in browser nor media library.
2. This options make the random_exclude_pattern obsolete, so it'd be better to replace it with this option.

I'm not sure what to do with (1).

Oh, ages indeed. I've been using this patch for over a decade, the PR is modern :-)

1. The "Exclude pattern for whole database" is misleading, because it's not considered in browser nor media library.

Actually it ought to be applied for media library as well, I see that my last commit here was a mistake. Going to revert. I rarely use media library. I can change the name of the config option and adjust the comments, and possibly rename the variable. But the idea is that it should still be possible to use the Browser to find things that are excluded by this option.

2. This options make the `random_exclude_pattern` obsolete, so it'd be better to replace it with this option.

I'd say they have different use cases. random_exclude_pattern only applies to add-random, I think it's fine to keep it. But, I see that it does not seem to be applied to AddRandomTag, is that an oversight? Feels like the exclude should apply also to the random songs found by artist/albumartist/album tags.

There, did some adjustments. I could also fix the random_exclude_pattern apply on AddRandomTag in a separate commit here, if that makes sense to you.

Rebased