b9AcE #NoEdits on Nostr: Mhmm, but what if you just can't see the output that a command is spewing at you ...

Mhmm, but what if you just can't see the output that a command is spewing at you because it's going too fast so it's just a blur of text?

Ah, then we go back to the times of telephone-modems (or before).
Modems and similar could get over-saturated, so they would scream "source quenched" (I think it was?) back at the sending side to halt transfer until the receiver was ready again.

You can do that too, now (usually).
If you just press <control>+s the command-line window's text should immediately stop scrolling (and once the outputting programs' internal buffers are full, they will temporarily halt until resumed too) so you can read what's going on, maybe scroll up to read what happened and maybe switch to another command-line window/[virtual]console to do other stuff, before you tell it to resume its output again with the <control>+q keypress, at which point everything should just resume (unless some program was incorrectly written, so the pause makes it crash, but if so then that's their bug to fix).