v0.2.6

Windows starts without the Visual C++ redistributable

The Windows build linked VCRUNTIME140.dll, which is not part of Windows — it arrives with the
Visual C++ redistributable. Without it the program did not start at all: Windows put up its own
dialog saying it could not be started and that reinstalling might fix the problem, which is a lie
in a helpful voice, since reinstalling brings the same binary and the same missing DLL. Reading the
shipped executable's import table on a Windows 11 machine confirmed it. The C runtime is linked
into the binary now, so there is nothing left to be missing.

Selecting by dragging follows the mouse while the conversation scrolls

Scrolling with the button still down slid the whole highlight away from the pointer, so dragging
out to the edge and scrolling to reach further took in nothing new. The two ends move differently
now while the button is down: the anchor travels with the word it was put on, and the end under the
pointer stays on its cell. Carrying both together is right once the button is up, and still is.

A selection being made is also no longer thrown away by scrolling — that is how one longer than the
screen gets made — and an anchor scrolled out of sight comes back to the line it was put on rather
than to the edge it was held at.

The frame around a code block is no longer copied

Dragging across a code block came back with ┌─ powershell and └─ wrapped around it: drawn by
the screen, written by nobody, and nothing a shell will take. A table keeps its border, which is
the same characters doing a different job.

/update looks before it closes anything

/update on an up-to-date copy tore the conversation down to print "already the newest" at a shell
prompt. Closing the screen is what hands the installer the terminal, so it used to happen first and
the check came after. It now asks first, and only an answer that names a release closes anything.

Switching into a session that is still working shows it working

It read the session's past and then sat idle with no live updates. The live feed was being opened
from a path a switch never travels.

Also

• A new-version notice under notify went to the status line, which "connected" took a moment
  later. It goes into the conversation now.
• With two windows open, /config in the second showed the settings that window loaded at launch
  and could save them back over the first one's change. It reads from disk when it opens.
• /help lists the other names a command answers to — /quit is also /exit, /changes also
  /diff. The parser always took them; nothing said so.

What changed

• fix(windows): link the C runtime statically, and four selection/update fixes
• style: wrap the code-fence test the way rustfmt does
• test(pty): judge the yank by the word coming back, not by finding it joined

Full diff

Install

curl -fsSL https://github.com/attacca-cc/zyris-code/releases/latest/download/install.sh | sh   # macOS, Linux
irm https://github.com/attacca-cc/zyris-code/releases/latest/download/install.ps1 | iex        # Windows

To pin this version: ... | sh -s -- --version v0.2.6.

Everything else — what it does, how to run it, every environment variable —
is in the README.

Verifying a download

Every archive is listed in SHA256SUMS, which the install scripts check before
unpacking anything. By hand:

sha256sum -c SHA256SUMS --ignore-missing

Files

Platform	Archive
Linux x86_64	zyris-code-x86_64-unknown-linux-gnu.tar.gz
Linux aarch64	zyris-code-aarch64-unknown-linux-gnu.tar.gz
macOS Apple silicon	zyris-code-aarch64-apple-darwin.tar.gz
macOS Intel	zyris-code-x86_64-apple-darwin.tar.gz
Windows x86_64	zyris-code-x86_64-pc-windows-msvc.zip

A platform missing from the release means its build failed; the others are
published regardless.