diff options
Diffstat (limited to 'src/detached/wire.zig')
| -rw-r--r-- | src/detached/wire.zig | 20 |
1 files changed, 11 insertions, 9 deletions
diff --git a/src/detached/wire.zig b/src/detached/wire.zig index a84c2a68..23a85158 100644 --- a/src/detached/wire.zig +++ b/src/detached/wire.zig @@ -39,16 +39,18 @@ //! frontend must not have to have been built with the core's options — so it is //! ALWAYS on the wire and dropped on arrival by a build with nowhere to put it. //! -//! WHAT IS NOT HERE. The seam has twenty-one methods; this carries FIVE of +//! WHAT IS NOT HERE. The seam has twenty-two methods; this carries FIVE of //! them — `push_present` as `frame`, `push_set_clipboard`, -//! `pull_read_clipboard`, `push_open_link` and `push_detach` — and the sixteen -//! it does not are named here with their reasons. The five are spelled out -//! because this arithmetic has now gone stale twice in one day, once when the -//! machine-local eight moved into the daemon and once when `detach` arrived, -//! and a count nobody can check against a list is a comment that rots quietly. -//! * The eight machine-local ones — `push_spawn`, `push_pty_write`, -//! `push_pty_resize`, `push_write_file`, `push_write_dump`, -//! `push_watch_file`, `push_watch_theme`, `push_dump_themes` — are +//! `pull_read_clipboard`, `push_open_link` and `push_detach` — and the +//! seventeen it does not are named here with their reasons. The five are +//! spelled out because this arithmetic has now gone stale twice in one day, +//! once when the machine-local eight moved into the daemon and once when +//! `detach` arrived, and a count nobody can check against a list is a comment +//! that rots quietly. +//! * The nine machine-local ones — `push_spawn`, `push_pty_write`, +//! `push_pty_resize`, `push_pty_signal`, `push_write_file`, +//! `push_write_dump`, `push_watch_file`, `push_watch_theme`, +//! `push_dump_themes` — are //! performed by the detached core ITSELF, through `host_io.zig`. A unix //! socket means it is on the same machine, so there is no question of //! whose disk or whose process table is meant, and a pane's shell has to |