# Changelog ## Unreleased - `pardes` has commands, and they describe themselves: `ps`, `attach`, `kill` and `new` for sessions, `do WORD` and `words` for the builtins, `fs ls|read|write|ask|follow|stat|help|complete PATH` for the tree (a refusal in the session's own words, where a mount says EINVAL), and `help`, `completion bash|fish|zsh`, `skill` and `version`. `pardes help` is a map of them; `help CMD` ends in examples; `help WORD` and `help PATH` print what the session's /commands and /README say, and with no session running, what a core made in the command's own process says. A command acts on `-s NAME`, else `$PARDES_9P`, else the only session. `pardes FILE` and every flag work as before; `--ps`, `--attach`, `--kill`, `--kill-all`, `--help` and `--version` are the commands' old spellings, for a release. A file named like a command opens as `./ps`. The reference's "The pardes command" is `pardes help --all`, written by `zig build builtins-json -Dplatform=tui`, and a test says when it is stale. - A drag draws no guide lines: no dashes where a pane or column would land, no rail for a carried column, no dashed seam under a pane rule held. The line between two columns no longer resizes them (nor, at a pane's corner, the panes too): a press there is a press in the pane. A column resizes by its box, left of its tag; a pane by its own box, or in a window by the rule above it. - An edit to the core recompiles it about 3 s sooner (`core-test`, 13 s to 10 s): the build keeps each grammar's highlight patterns that pardes colours once, where every compile of every program that takes the core did it again, a quarter of its time. A package that depends on pardes is given the same filtered queries. - The core measures a grapheme's cells over uucode itself (`File.utf8Width`, libvaxis's `gwidth` to the cell on every scalar value), so libvaxis is the tui's and the gui's alone, not the core module's. The 256-colour palette Petscii art and the window draw a palette colour with is pardes's own (`colors.xterm`), ghostty-vt's default to the entry. A `+Pager` (`pardes -`) reads its program's colour codes with a parser of its own, which pages what ghostty-vt's did, byte for byte, about 10% faster. - Commit patches open as `+Diff-` and reuse only their own commit's pane, so another paged patch no longer replaces one already open. - zstbi is upstream's again (zig-gamedev/zstbi, its main): the fork pinned for Zig 0.17 was deleted, and a fresh checkout could not fetch it. - pardes's syntax is a library: a Zig package that depends on pardes is given the `pardes-syntax` module (`src/lib_syntax.zig`), with the grammars, highlighting, declarations, syntax tree and themes as the editor has them, for a program that draws source text itself. Every dependency but tree-sitter's runtime is lazy in the manifest, so such a package fetches the runtime and the grammars of its `tree-sitter` set and nothing else; `zig build lib-test`, which `unit-test` runs, builds one (`test/lib`). The markdown grammar is pinned by its commit: its branch has moved, and a fresh checkout could not fetch it. - Enter, `o` and `O` give the new line helix's indent where the file's grammar has an indent query (bash, C, C#, C++, Clojure, CSS, Elixir, Fortran, Go, HTML, Java, JavaScript, JSON, Kotlin, OCaml, PHP, Python, Ruby, Rust, Scala, Zig), from the file's syntax tree; elsewhere the line's indent as before. Enter between a pair (`()`, `[]`, `{}`, quotes) puts the closer on a line of its own and the cursor on one a level in. A closer typed on its own line stays where it is typed, as in helix. - A session's end (`Exit`, the last pane's `Del`, its terminal or window gone) leaves a slim dump in the state file: its panes with their files, directories and places, not a clean file's text, an undo history or a terminal's screen. `History` (`SPC f h`) lists the state file's dumps in a `+History` pane, each as the command that brings it back, `Restore