Escape codes for links aren't always suppressed when not supported

[emojjon]

Discussed in #1625

^{Originally posted by emojjon October 28, 2021}
As I understand it, you can't create an instance of Console that explicitly doesn't use link escape codes. Apparently these codes should be ignored by terminals that don't support them. Sometimes it would be good though, because the codes actually mangles the output in some circumstances.

I hesitate to say exactly how to reproduce this since in my case it involved several ssh logins and strangeness with shell rc-files and what not. Suffice to say it would be nice to be able to turn it off in some circumstances, perhaps even from outside the python code (environment variable?).

Great project by the way. I discovered it yesterday, and I'm looking forward to try and use it myself.

[willmcgugan]

Closing for now since I can't reproduce. But happy to look at it again if we can narrow down the cause.

[github-actions]

Did I solve your problem?

Consider sponsoring the ongoing work on Rich and Textual.

Or buy me a coffee to say thanks.

– Will McGugan

[jamie-pate]

In concourse it prints out ansible-lint output like this, as there's no way afaik to signal that this is not supported:

]8;id=274247;https://ansible-lint.readthedocs.io/rules/syntax-check/\syntax-check[specific]]8;;\: Invalid options for ansible.builtin.include_role: vars

https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda#backward-compatibility mentions that any terminal emulator that doesn't parse it correctly should consider this a bug since it doesn't properly follow ECMA-48