It would be nice to have a 'conflicted' keyword for --match which matches the
patches in the last conflictor(s) in the repository, that is, the patches
involved in any 'live' conflict.

That way, you can see the 'live' conflicts with darcs changes --match conflicted

This would make it especially convenient for solving conflicts using unpull or
unrecord, for when you have draft work conflicting with upstream work.

Merging in issue1588 which wants the opposite (would be covered by --match 'not
conflicted')

I guess there is an open question to resolve before we can implement this: I
mostly remember matchers as working only on PatchInfo (although the touch
matcher  changes this, I think).  Can we implement this with just local changes
to Darcs.Match, or does the rest of darcs need to be passing more information up
to it?