Exploiting the stroboscopic effect from emerge output

[nokilli]

So, I have a nice system. An Asus Zenbook, one of the newish ones, and it's USB-C to the 4K display (and then actually another via DisplayPort daisy-chain.)

Wayland on this thing is incredible. I'm running emacs in terminal mode, on foot, on sway. Transparency is on. Intel xe integrated graphics (deserves own post.)

And sometimes when I do an emerge, the text is flying by so fast that some kind of stroboscopic effect occurs and I can see specific lines in the output as if it's standing still.

Like how if you're driving and you look down at a passing vehicle's wheel and it looks like it's actually going reverse but very slowly? Best way I can explain it.

Anyways...

A few times the line being accentuated actually contains useful information. Like the file name being compiled or the package or some path fragment. Enough information to sort of tell what is going on.

Even though the text is flying by so fast that no human being could possibly hope to read it, I can pick out useful detail about the status of the emerge owing entirely to this stroboscopic effect.

(and it's a 60fps monitor, I can only imagine what a gaming monitor would be like)

Everything is measurable here, yes? What would be the engineering approach to attempt to exploit this, to force it, to control it both so that the effect occurs but also then that useful information be highlighted so? Is that even remotely possible? Like maybe, trying to pad every compile with some forced time interval?

6.12 has RT! What an absolutely amazing artifact it would be to make compiling cool again!
_________________
Today is the first day of the rest of your Gentoo installation.