[rsmmr]

The compact terminal output now signals test progress via OSC 9;4
escape codes.[^1] A number of terminal emulators support those these
days, and those who don't should just be ignoring them.[^2]

[^1] https://learn.microsoft.com/en-us/windows/terminal/tutorials/progress-bar-sequences

[^2] This comes with a work-around for older iTerm2 versions that,
rather than ignoring, would end up triggering notifications for these
escape codes instead of showing a progress bar.

[rsmmr]

Would be nice to get this into 8.1, anybody up for a review?

[bbannier]

I briefly looked at this when you first put it up and was wondering why this couldn't be collected in a single, separate OutputHandler (does this even need to be a Console?). That would prevent this feature being spread all over the place. That said, I also wondered whether this would actually be worth adding at all.

[awelzel]

That would prevent this feature being spread all over the place. That said, I also wondered whether this would actually be worth adding at all.

I think so. pytest, systemd and other tools are adding it, so why not 🤷‍♂️

[rsmmr]

I briefly looked at this when you first put it up and was wondering why this couldn't be collected in a single, separate OutputHandler (does this even need to be a Console?).

It's escape codes, so it needs a TTY, that's why it's inside a console, where we are printing other escape codes already as well. And it's inside the CompactConsole because limiting to that felt most natural to me as that one is already "somewhat graphical". That said, I can see creating a separate OutputHandler for it if that feels better.

That said, I also wondered whether this would actually be worth adding at all.

I find it quite useful.

[awelzel]

And it's inside the CompactConsole because limiting to that felt most natural to me as that one is already "somewhat graphical"

Ah, can this easily be lifted into the Console one? I understood this more as having a terminal window in the background or in a separate tab and then the taskbar or the tab list shows the progress indication. For these compact vs normal should not matter.

[rsmmr]

Ah, can this easily be lifted into the Console one?

Yes, it can.

[rsmmr]

I'm not a kitty user, but doesn't look like. I don't have LC_TERMINAL / LC_TERMINAL_VERSION here and these don't look super useful for fingerprinting.

Ok, this lets me re-consider the default-on approach. Seems potentially annoying, also given that we have two examples now where older terminal versions trigger notifications instead; there may be further ones too then. So I pushed an update that adds a new command-line option and environment variable to enable. I've switched to an output handler now as well, as that indeed works pretty well with the opt-in approach. See what you guys think.