v0.7.2

nocx 0.7.2

After updating to 0.7.1, some people found every command stuck in a Running block, in
local panes and over ssh. This patch fixes the causes.

Updating no longer leaves you on the old background process

A new version could attach to the background process the previous version had started, so
the window said 0.7.2 while the process running your shells was still the old one — and
every fix that lives in the shell integration was silently absent.

A different version now takes over: the new window starts its own process, sessions you
already have keep running under the old one until they end, and new panes use the new
version. Nothing is stopped by hand.

A host that still has an old integration finishes its first command again

Some hosts carried a startup line from an older nocx that sourced an old copy of the
integration. That copy is retired when nocx publishes to the host, so the first command in a
remote pane completes instead of leaving a block that never ends.

Helper mode asks before it installs

A connection set to Helper mode whose permission had never been recorded used to deliver no
integration at all: it behaved as a plain terminal, and said nothing about it. It now asks
the first time you connect to a host, once per host — granted, the helper is installed and
used; refused, it is not asked again. A dismissed question refuses the connection, and the
pane says the connection is waiting for an answer.

A pane says when its shell integration could not be copied

If nocx could not copy the shell integration to a host, the failure was written to a log and
the pane carried on as though nothing had happened. It now says so, once, and stays usable.

A slow remote shell no longer ends up without blocks

Connecting to a host can take a while — the connection, the copy and the cleanup all happen
before your shell starts. That time used to count against the shell, so a slow host could end
up as a plain terminal with no blocks at all. The wait is now measured from two separate
moments: the connection getting ready, and the shell running without answering. A slow host
works, and a shell that truly never answers still falls back to a plain terminal.

How to update

brew upgrade --cask nocx

Nothing needs to be killed by hand: the new version takes over from the old one as it starts,
and your sessions keep running.