In fairness, I don't think the nested playlist feature suggested in the wishlist includes these types of merges. I don't know if this is the easiest way to dev 'AND OR NOT' into playlist building but it does seem very easy for the end user. Especially if existing playlists can simply be dragged into an 'X' playlist node.

If you check in the wishlistyou will see that nested playlists are allready requested and considered as high priority. So is better to support the specific posts than adding a new one. This is also the reason why people don't answer to your post...

Yes, I would like something like this.

As no one else has replied I will. I think this sounds like a very useful feature for advanced users, but I personally would never need anything so complex. Reading the forums it does sound like you're not alone though! Good suggestion.

I am a bit dazzled as there wasn't a single statement/reply to my suggestion. Have I descibed it poorly or is it just too much aloof or complicated?

A little feedback from the community would be appreciated!

I have read already several times that people want to have operators like AND and OR for building up there autoplaylists. I'm missing that, too.

I have a suggestion. For optimal flexibility you could solve this with nested playlists. Example of how it could work:
* You build an (auto)playlist A
* You build an (auto)playlist B
* You build a playlist X with option AND (this option thing would be new)
* You put A and B below X

AND would mean: All songs that are in A AND B (= intersection)
OR would mean: All songs that are in A OR B (= union)

This can be nested over several levels to build more complex criteria. AND and OR nodes can also carry several lists below (not only 2). And to make it perfect we could have a NOT node/playlist.

This feature would be extremely powerful and quite easy for users to handle!