You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`GhosttyKittyGraphicsPlacementIterator`| Managed iterator over Kitty placements. |
@@ -59,10 +64,30 @@ If you want Ghostty behavior inside RoyalTerminal, you usually begin with the ma
59
64
60
65
These are the types used by RoyalTerminal itself when it wants native VT behavior without forcing consumers to work directly against raw pointers and C structs.
61
66
67
+
## Engine-neutral effects and Unicode
68
+
69
+
Hosts that can use either VT engine should query the terminal contracts instead
|`ITerminalUnicodeWidthProvider`| Codepoint width and first-grapheme width using the active engine's rules. |
76
+
77
+
`GhosttyVtProcessor` implements these contracts with the normalized
78
+
libghostty callbacks and Ghostty Unicode tables. `BasicVtProcessor` implements
79
+
the same contracts with managed OSC parsing and RoyalTerminal Unicode tables.
80
+
The effect callbacks are policy boundaries: applications still decide whether
81
+
clipboard writes and desktop notifications are allowed.
82
+
62
83
## The raw VT mirror is also public
63
84
64
85
Under those wrappers, `GhosttyVtNative` exposes the Ghostty VT ABI directly. This is not the right layer for most applications, but it is the right layer for advanced interop, diagnostics, or custom wrappers.
65
86
87
+
At the current Ghostty revision, `TerminalNew` takes `columns` and `rows`
88
+
directly. Configure the returned terminal through `TerminalSet`; the former
89
+
`GhosttyTerminalOptions` constructor struct no longer exists.
0 commit comments