When emerge displays the atoms it will/would merge (for example in `emerge -au @world') it ususally prints the atoms inside of @world bold.
But I have some atoms, which aren't listed in @world but in a world_set instead.
I think the atoms from world_sets should be printed out bold, too, as they are selected when updating/installing/... @world.
Yeah, that's true.
Also see bug 577720 which is very similar to what your are asking for, but not exactly the same thing (since the implementation for bug 577720 does not involve world_sets at all, though there is often overlap between world_sets and user sets).
FWIW, this behavior would solve my original use case as well.
I think the best course of action would be to revert my patch for bug 577720 and implement the behavior as described here. A lot of the complications from that patch could be eliminated, and extra configuration would not be required.
It would be difficult to keep both, since packages that are in user sets flagged in world_sets could only be colorized one way or the other, which I'm sure would lead to confusion.
The downside is that this is a new behavior that couldn't be changed by configuration, but I agree with all of the original reasoning.
I'm willing to implement this if the maintainers agree.
(In reply to Adam Mills from comment #2)
> I'm willing to implement this if the maintainers agree.
Yeah, I like this idea. I think it makes more sense, since world_sets is actually what gets pulled into the dependency graph.
This is fixed in git: <https://gitweb.gentoo.org/proj/portage.git/commit/?id=40cdc1c3f467ac94d3a966777eb6a0907c269550>
Released in portage-2.3.0.