ah, disregard that comment about the swim lanes, I misunderstood what this code was doing.

but in general I think there are some questions about exactly what we want the v2 console UI to look like, especially with regard to logs vs "normal" console output

and allowing scrollback vs. letting the swim lanes display information dynamically

So my next best guess is to interleave the “normal” output with the logs line-by-line, and leave it to the console rule authors to figure out when they want to print stuff. If someone wants something printed at the end of an execution (like the json output of

./pants export

), they can print it at the end of their console rules, when no more products are being requested.

That solution also has some flaws though

I don’t think that most users care about streaming succeeding tests, but they care about seeing tests fail ASAP

but I think setting the terminal into raw mode is breaking natural scrollback, regardless of whether or not we put the swim lanes at the bottom of the terminal

if I use tmux scrollback I just see the same swimlane lines repeated, which I think is what you would expect if we are repainting the terminal in a loop ever 50ms or whatever the value is

well, i think it depends how much of the screen you clear, right?

(i reaaaally don't know.)