diff options
Diffstat (limited to 'docs/macos.md')
| -rw-r--r-- | docs/macos.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/macos.md b/docs/macos.md index 3ee55d0a..ddd7eee1 100644 --- a/docs/macos.md +++ b/docs/macos.md @@ -77,7 +77,7 @@ fourteen are filled in (`src/macos.zig:1761`). The machine-local half of those methods is no longer this file's. `forkShell`, `writeFileBytes` and `writeFd` live in `src/host_io.zig` and are shared with -the tty shell, the SDL shell and the detached daemon; `src/macos.zig` calls +the tui shell, the SDL shell and the detached daemon; `src/macos.zig` calls them (`:1807`, `:1823`, `:1848`, `:1863`) and its own copies, together with the four `extern "c"` declarations they needed (`forkpty`, `execv`, `chdir`, `_exit`), are gone. Two `extern "c"` declarations remain here: `setenv`, and @@ -473,7 +473,7 @@ has none: between fork and exec can deadlock on the heap a pty reader thread was holding. Every pane is emulated by the bundled VT, so the value describes pardes and never the terminal pardes was started from; `-Dplatform=gui` and - the tty shell take the same path, where the difference is only that their + the tui shell take the same path, where the difference is only that their launcher usually happened to set something. The names come from `config.child_term` / `child_colorterm` / `child_term_program`, and `TERM` is deliberately `xterm-256color` rather than a name with no installed @@ -586,7 +586,7 @@ theme it cannot. showed *nothing at all*: with `native_images` false the core assumes a terminal that cannot draw pixels and degrades a document to counted page turns, and this host never set it. It does now — this shell draws pixels, which is a fact -rather than a question (the tty backend has to ask the terminal about +rather than a question (the tui backend has to ask the terminal about kitty-graphics support; the SDL one just says yes, as we do). The transport is `pardes_image_s`, walked with `pardes_frame_images` / @@ -1122,7 +1122,7 @@ used for the table and is not folded into the direct-path claim. ## Not implemented - **The `lsp` effect.** Needs a worker plus a snapshot of the pane's path and - content taken *before* it starts, as `LspJob` in `tty.zig` does; the core + content taken *before* it starts, as `LspJob` in `tui.zig` does; the core keeps editing while a query is in flight. Until then every query is answered with an EMPTY `lsp_resp` rather than dropped — dropping one leaves the keystroke that asked (insert-mode Tab after a dot) waiting forever, and dead |
