6e34bc686c
Previously ghostty_terminal_set required all values to be passed as pointers to the value, even when the value itself was already a pointer (userdata, function pointer callbacks). This forced callers into awkward patterns like compound literals or intermediate variables just to take the address of a pointer. Now pointer-typed options (userdata and all callbacks) are passed directly as the value parameter. Only non-pointer types like GhosttyString still require a pointer to the value. This simplifies InType to return the actual stored type for each option and lets setTyped work with those types directly. |
||
|---|---|---|
| .. | ||
| c-vt | ||
| c-vt-build-info | ||
| c-vt-cmake | ||
| c-vt-cmake-static | ||
| c-vt-effects | ||
| c-vt-encode-focus | ||
| c-vt-encode-key | ||
| c-vt-encode-mouse | ||
| c-vt-formatter | ||
| c-vt-grid-traverse | ||
| c-vt-modes | ||
| c-vt-paste | ||
| c-vt-render | ||
| c-vt-sgr | ||
| c-vt-size-report | ||
| c-vt-static | ||
| wasm-key-encode | ||
| wasm-sgr | ||
| zig-formatter | ||
| zig-vt | ||
| zig-vt-stream | ||
| .gitignore | ||
| AGENTS.md | ||
| README.md | ||
README.md
Examples
Standalone projects demonstrating the Ghostty library APIs.
The directories starting with c- use the C API and the directories
starting with zig- use the Zig API.
Every example can be built and run using zig build and zig build run
from within the respective example directory.
Even the C API examples use the Zig build system (not the language) to
build the project.
Running an Example
cd example/<dir>
zig build run