^[control-codes live in libghostty-vt

Operating system commands

OSC 702 Report Version

Ask rxvt-unicode for its name and version.

OSC 702 ; ? ST
ECMA-48
§8.3.89 OSC – Operating System Command, p. 51
Specification
urxvt(7), XTerm Operating System Commands

OSC 702 ; ? ST asks rxvt-unicode who it is. It answers OSC 702 ; rxvt-unicode ; name ; major ; minor, ended the way the request was, with name the resource name it runs under, such as urxvt. The manual’s example is version 7.4 (urxvt(7)). Only ? does anything. rxvt-unicode’s source takes the major and minor numbers as single characters of its version string, so 9.31 reports a minor version of 3. XTVERSION is xterm’s way to ask the same.

A default xterm has no OSC 702 and ignores it (the OSC numbers it knows). The cases follow xterm.

libghostty-vt does not recognize OSC 702 either: its OSC parser in osc.zig has no state for the number, so the string is dropped, and the cases pass.

Support

TerminalVersionSupportNotes
VT220manual, 2nd ed., 1984NoOSC is not among the controls it recognizes (§4.2)
VT510manual, 1st ed., 1993Noignores an OSC string (chapter 4)
xtermpatch 412, xterm-411aNoignored
libghostty-vt83edd49Noignored
Konsole26.11.70, a24c3d71Nonot among the OSC numbers it handles (Vt102Emulation.h)
ConEmubuild 230724, its documentationNonot in its ANSI escape codes
rxvt-unicode9.31, urxvtperl(3)Yesname, resource name, major and minor version (urxvt(7))

Validation

OSC702-1: Not answered

\e]702;?\a
|______|
reply none
Every example on these pages runs in your browser, in libghostty-vt compiled to WebAssembly.