Appearance
TBC clear tab stop (CSI g)
CSI Ps gTBC (Tab Clear) clears tab stops.
CSI 0 g clears the tab stop at the current cursor position; CSI 3 g clears all tab stops. After clearing all tab stops, tab characters have no effect (cursor does not advance). TBC is used together with HTS to set up custom tab stop patterns for formatted output.How this is testedautomated
Clear all tab stops with
Clear all tab stops with
\x1b[3g, send a tab from column 0 — verify cursor does not advance (stays at column 0), confirming all tab stops were cleared.The same probe runs against headless backends (via Termless) and real terminal apps (via a daemon launched in each terminal). This lets us distinguish parser correctness from rendering correctness.
Analysis2026-04-06
Not supported by any tested terminal. Part of the Core TUI baseline.
Supported by 0 of 14 backends (0%)
Terminal Applications
| Terminal | Version | Support | Notes |
|---|---|---|---|
| iTerm2 | 3.6.9 | ✗ no | cursor at col 80, expected 1 |
| Ghostty | 1.3.1 | ✗ no | cursor at col 270, expected 1 |
| VS Code | ✗ no | ||
| Warp | ✗ no | ||
| Cursor | ✗ no | ||
| Terminal.app | ✗ no |
Headless Backends
Parser correctness only — a ✓ means the parser accepts the sequence.
| Backend | Version | Support | Notes |
|---|---|---|---|
| Alacritty | 0.26.0 | ✗ no | Tab stop clear (TBC) not exposed via alacritty_terminal API |
| Kitty | 0.40.0 | ✗ no | Tab stop clear (TBC) not exposed via Python batch bridge |
| vt100.js | 0.2.1 | ✗ no | Tab stop manipulation not implemented in vt100.js |
| vterm | 0.2.0 | ✗ no | Tab stop manipulation not implemented in vterm.js |
| WezTerm | 0.1.0-fork.5 | ✗ no | Tab stop clear (TBC) not exposed via wezterm-term API |
| xterm.js | 5.5.0 | ✗ no | Tab stop clear (TBC) not implemented in xterm.js headless mode |