branderson
d76d2f4b3a
Nvim isn't a single process attached to the terminal: the process that actually spawns jobs (clipboard-copy included) is a separate `nvim --embed` core process with no tty of its own (ps shows `?`); the real pty belongs to a distinct parent UI process. Checking only the immediate parent's tty (as the previous fix did) found the embed process's `?` and fell through to the broken /dev/tty path every time in real interactive use, even though it looked fine in headless testing. Walk up the process tree past any tty-less ancestors instead. Verified against the real docker-compose path in actual (non-headless) TUI mode, with real keystrokes fed through a pty: the OSC 52 sequence now reaches the terminal with no error, where it previously still failed.