Created attachment 638570 [details] full emerge output at the current time I'd be fine with it being a flag, like --show-tasks Maybe it could output like: >>> Installing (50 of 54) kde-frameworks/baloo-5.70.0::gentoo >>> Emerging (51 of 54) kde-frameworks/purpose-5.70.0::gentoo >>> Installing (51 of 54) kde-frameworks/purpose-5.70.0::gentoo >>> Emerging (52 of 54) kde-frameworks/kross-5.70.0::gentoo >>> Installing (52 of 54) kde-frameworks/kross-5.70.0::gentoo >>> Emerging (53 of 54) kde-frameworks/khtml-5.70.0::gentoo >>> Installing (53 of 54) kde-frameworks/khtml-5.70.0::gentoo >>> Emerging (54 of 54) kde-plasma/plasma-meta-5.18.5::gentoo >>> Installing (54 of 54) kde-plasma/plasma-meta-5.18.5::gentoo [[[ #19 app-office/libreoffice-6.4.3.2::gentoo src_compile ]]] [[[ #20 dev-lang/rust-1.43.1::gentoo src_compile ]]] [[[ #35 www-client/palemoon-28.9.3::palemoon src_compile ]]] >>> Jobs: 51 of 54 complete, 3 running Load avg: 5.45, 5.46, 5.80 Or something like that. The key aspect is really the "[[[]]]" aspect that exposes current tasks regardless of where they are in the build order, which, as in way my case, was long long ago, due in part to how all those things have monster compile times, and have no things depending on them, which allows them to be built concurrently ... Tasks that are completed could be folded into ">>>" lines when they're done. Perhaps some sort of limit to how many lines are emitted, or maybe a way of condensing multiple tasks into a line, but that's mostly a concern for the amount of "draw" work required to display this sort of thing. Though of course the idea here is people who want this output verbatim in a log somewhere without lots of term hacking, would simply not use this option. This would help me not assume the worst, like: - Is kde-plasma/plasma-meta for some profound reason taking forever to install and consume reams of CPU? - Is portage hung and getting confused? And it would eliminate the need to crack open htop and go fishing through my process tree. It doesn't need the full granularity of phase's if that's too hard, I just stuck that in there in case it was easy to do, a simple "[#number emerging|installing package]" would also suffice. But if adding granularity is free, then go for it. I've attached a fair chunk of my emerge output, with the "build plan" for a little context on why the status quo is confusing.
