Tracking issue for -Zterminal-urls

[workingjubilee]

This is a tracking issue for the MCP "-Zterminal-urls" (rust-lang/compiler-team#587).

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps

• Implementation:
  • Introduce -Zterminal-urls to use OSC8 for error codes #107838
• Adjust documentation (see instructions on rustc-dev-guide)
• Stabilization PR (see instructions on rustc-dev-guide)

Unresolved Questions

• Has T-compiler coordinated with T-cargo on their concerns? Teach rustc to use OSC8 on nightly / Embedded links in terminal output compiler-team#587 (comment)
• What should we include links for?
  • Currently, error codes: Introduce -Zterminal-urls to use OSC8 for error codes #107838
  • Lints? use osc 8 hyperlinks to link to the reference for lints when they are printed #125528
• Should we allow configuration of link amounts? Is that a non-boolean argument?
• Can we autodetect terminal support? Should we?

[workingjubilee]

cc @estebank @epage

I know many MCPs, much less unstable CLI options, don't get a tracking issue. But we need something if T-compiler and T-cargo are going to coordinate on this, so this seems like The Thing. If there is any serious discussion please open a new issue and pingback this.

[epage]

See also https://rust-lang.zulipchat.com/#narrow/stream/147480-t-compiler.2Fwg-diagnostics/topic/Richer.20diagnostics.3F/near/430145899