Skip to content

Conversation

@bluetech
Copy link
Member

Due to compatibility issues with some terminal emulators. Can maybe try again in a few years.

Fix #13896.

@bluetech bluetech added the backport 9.0.x apply to PRs at any point; backports the changes to the 9.0.x branch label Nov 14, 2025
@psf-chronographer psf-chronographer bot added the bot:chronographer:provided (automation) changelog entry is part of PR label Nov 14, 2025
@nicoddemus
Copy link
Member

Oh this is a shame, it works well for ConEmu.

Could we try to keep the compatible ones working instead?

@The-Compiler
Copy link
Member

The-Compiler commented Nov 14, 2025

nsI agree completely removing it would be a shame! I'm for either:

  • Adding a configuration option to opt into it
  • and/or enabling it on Windows by default (where the chance seems much higher that someone runs a compatible terminal and actually has the progress visible somewhere useful in the UI)

For the former, there is a risk we're polluting things with a new config option that won't be needed anymore hopefully a year down the line. At the same time, maybe there is still new/exotic/... terminal emulators that implement this the "broken" way (really a shame two extensions use the same number...), so it might still be needed in exotic cases.

@bluetech
Copy link
Member Author

OK, I think we can do this:

  • Disable by default, except on Windows (low risk).
  • Allow to enable using -p terminalprogress.
  • In a few years, consider enabling by default again.

I will send another PR for this.

@bluetech
Copy link
Member Author

Replaced by #13971.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport 9.0.x apply to PRs at any point; backports the changes to the 9.0.x branch bot:chronographer:provided (automation) changelog entry is part of PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

terminalprogress causes thousands of iTerm2 alerts

3 participants