Bohdan Triapitsyn
39fa8c1917
The terminal ran on the ghostty-web npm package plus a hand-written patch, and every rendering bug (recycled rows, duplicated reflow fragments, prompt artifacts) had to be worked around from outside. The emulator now is the official libghostty-vt C ABI compiled to WebAssembly, driven by a browser adapter ported from T3 Code (MIT, notice in LICENSE-T3CODE) and owned in packages/ui/src/lib/ghostty. The artifact is reproducible with scripts/build-libghostty-wasm.sh, including a workaround for Zig 0.15.2 on macOS 27 SDKs. On top of the port: one WASM instance per page with every tab kept mounted and hidden tabs paused; history replayed at the PTY size it was drawn for; shells spawned only after the first fitted grid so zsh never prints the PROMPT_SP marker; box drawing, block elements and Powerline arrows drawn procedurally to the exact cell so TUI borders and block logos have no gaps between rows; a software-rasterized canvas so Gecko renders every tab's text with the same smoothing; the symbols-only Nerd Font bundled instead of a CDN fetch; touch selection and scrolling driven through the surface API; a copy button in the tab strip for touch hosts; localized aria labels. Testing: bun tests run the real WASM (reflow, palette, replay isolation, recycled rows, box glyph geometry); viewport and view tests use a surface double; verified in Chromium and Zen (windowed and headless) for crisp text, new tabs, panel reopen, resize and box glyph rendering; package type-check, oxlint/eslint on new files, web build.
13 lines
692 B
Zig
13 lines
692 B
Zig
// Callback trampoline for libghostty-vt's write-PTY option.
|
|
//
|
|
// libghostty-vt calls the PTY writer through its indirect function table, so
|
|
// the JavaScript host cannot pass a closure directly. This 112-byte module
|
|
// exports one function whose only job is to forward the call to an import the
|
|
// host implements. `build-libghostty-wasm.sh` compiles it and prints the bytes
|
|
// that `runtime.ts` embeds, so the browser never fetches it separately.
|
|
extern "env" fn openchamber_write_pty(terminal: u32, userdata: u32, data: u32, len: u32) void;
|
|
|
|
export fn ghostty_write_pty(terminal: u32, userdata: u32, data: u32, len: u32) void {
|
|
openchamber_write_pty(terminal, userdata, data, len);
|
|
}
|