Struct SpawnHandles 

pub struct SpawnHandles {
    pub pty: PtyHandle,
    pub snapshot: Arc<ArcSwap<TerminalSnapshot>>,
    pub term: SharedTerm,
    pub child_killer: Box<dyn ChildKiller + Send + Sync>,
    pub child_pid: Option<u32>,
}

Successful spawn handles.

Fields

pty: PtyHandle

snapshot: Arc<ArcSwap<TerminalSnapshot>>

term: SharedTerm

T3 (2026-05-25): shared handle to the alacritty Term the reader task drives. Dispatch-side actions (scroll, resize) lock the inner Mutex; the reader holds an Arc to the same Term. Cheap to clone.

child_killer: Box<dyn ChildKiller + Send + Sync>

2026-05-25: handle to the spawned child the TerminalBuffer::Drop uses to force the shell to exit on buffer teardown. Without this, the master-side reader fd (cloned via try_clone_reader) keeps the PTY open even after PtyHandle drops — the child never sees SIGHUP, the reader’s blocking read() never returns, and the editor freezes on :q. Calling killer.kill() sends SIGKILL to the child; once it exits, the reader’s read() returns 0 (EOF), the spawn_blocking task exits cleanly.

child_pid: Option<u32>

2026-05-25: child PID captured at spawn so Drop can follow the portable_pty SIGHUP with a SIGKILL fallback (libc::kill(pid, SIGKILL) on Unix). Some shells / environments don’t exit on SIGHUP reliably; SIGKILL is the guaranteed wake for the reader’s blocking read(). None when the platform doesn’t expose the PID (Windows ConPTY).