Is your feature request related to a problem?
There's no built-in way to render a hyperlink inside text. Terminals support OSC 8 hyperlinks (ESC ]8;;<url> … ESC ]8;;), which render as clickable links, but text only takes a string plus styling—so a CLI can't emit a clickable URL without hand-writing the escape sequence and fighting the renderer's U+FFFD substitution.
Describe the solution you'd like
Either a new link("value", { href: "https://example.com" }) util, or extending the text options with an optional { href }.
link("docs", { href: "https://example.com" });
text("docs", { href: "https://example.com" });
// emits: ESC ]8;;https://example.com ST docs ESC ]8;; STThe link text renders and measures like normal text; the OSC 8 open/close bytes are zero-width.
Describe alternatives you've considered
Putting the OSC 8 bytes inside the content string doesn't work today—they'd be mangled to U+FFFD. A verbatim-passthrough escape hatch (#66) would let you hand-roll it, but a first-class href option keeps width accounting correct and the call site readable.
Additional context
Failing test case on nm/repro/osc8-hyperlinks (test · diff).
Needs an href field on the text op (ops.ts)—or a link() helper that sets it—carried through the text decode in reduce (src/clayterm.c:562); the renderer emits the OSC 8 open before the run's glyph cells and the close after, both zero-width.
Is your feature request related to a problem?
There's no built-in way to render a hyperlink inside text. Terminals support OSC 8 hyperlinks (
ESC ]8;;<url> … ESC ]8;;), which render as clickable links, buttextonly takes a string plus styling—so a CLI can't emit a clickable URL without hand-writing the escape sequence and fighting the renderer'sU+FFFDsubstitution.Describe the solution you'd like
Either a new
link("value", { href: "https://example.com" })util, or extending thetextoptions with an optional{ href }.The link text renders and measures like normal text; the OSC 8 open/close bytes are zero-width.
Describe alternatives you've considered
Putting the OSC 8 bytes inside the content string doesn't work today—they'd be mangled to
U+FFFD. A verbatim-passthrough escape hatch (#66) would let you hand-roll it, but a first-classhrefoption keeps width accounting correct and the call site readable.Additional context
Failing test case on
nm/repro/osc8-hyperlinks(test · diff).Needs an
hreffield on thetextop (ops.ts)—or alink()helper that sets it—carried through the text decode inreduce(src/clayterm.c:562); the renderer emits the OSC 8 open before the run's glyph cells and the close after, both zero-width.