l0ng-ai 5fc97d5d06 docs(shell): put nushell on the page that lists integrated shells ...

The "Which shells" table named zsh, bash, fish and PowerShell. Nushell
has had the same treatment as the rest for as long as they have -- a
throwaway `config.nu` passed with `--config`, sourcing the user's own
back in -- and a nushell user reading that page concluded they got
nothing.

The row says how, including the part that makes it unlike the others:
`source` is parse-time in Nushell, so the path to your config is resolved
as the wrapper is written rather than checked when it runs.

The test reads the shells out of the injection dispatch, so a sixth has to
be written down before it passes; removing the new row fails it, naming
Nushell.

Found by checking a table against the thing it claims to describe, which
also cleared two nearby ones: `PATH_PROBED_SHELLS` holds twelve shells
against these five, and that difference is right -- probing PATH so a
shell can be chosen is not the same as having hooks for it, and ksh or
tcsh work fine without them.

2026-08-16 15:09:54 +08:00

..

tty7-cli

docs(cli): say that a newline inside send's TEXT presses Enter

2026-08-16 13:33:46 +08:00

tty7-core

docs(shell): put nushell on the page that lists integrated shells

2026-08-16 15:09:54 +08:00

tty7-server

fix(resize): defer the reflow to the daemon's Size echo on remote routes too (#632)

2026-08-14 16:02:04 +08:00