krino.git/cmd/krino/render_test.go, branch v0.0.12rule-based file sorter in Go, shows the plan before touching anything, applies only the files you choose, and can undo any run, with s-expression rules and a GTK 4 windowhttps://git.labunix.xyz/krino.git/atom?h=v0.0.122026-09-17T10:54:06Zthe module path is git.labunix.xyz/krino2026-09-17T10:54:06ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T10:54:06Zurn:sha1:1884d56b0d399e9cdb80016a9c166b0120989933
So that go install can find it. cgit serves no go-import meta tag, so
nginx answers a ?go-get=1 request for /NAME with one pointing at
https://git.labunix.xyz/NAME.git; the alternative was carrying a .git
suffix through every import line forever.
One sed over the imports, both go.mod files, and the dependency gate's
whitelist. Nothing else depends on the path. go install works from the
next tag, the first release whose go.mod carries it.
comments that explain the code, not how it was written2026-09-17T10:11:42ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T10:11:42Zurn:sha1:bddbd74e4a73e8e32bcf648efd1cac5655f6d0cd
About 340 comments cited the development process: task and plan
numbers, fix waves, rulings, reviewers, and the author in the third
person with a date. None of that exists outside the work itself, so to
a reader it pointed at nothing. Each one now states the engineering
reason it was standing in front of; where a comment was provenance and
nothing else, it is gone.
References to docs/design.md and docs/gui-design.md by section stay:
both ship with the repository. The design documents lose their
amendment diaries - CHANGELOG.md is that record - and the GUI's says
plainly that the window has gone further than the document.
Only comments changed. Every .go file was parsed and its code printed
with comments stripped, before and after: the two hashes are identical
across all 175 files.
review and undo headings wrap past the label column; format characters take a column2026-09-14T22:29:09ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:29:09Zurn:sha1:17e933a16ff7de1b06d62504e78c40e615c8b553output: wrap by terminal columns, names cannot fake step lines, -v lists unscanned destinations2026-09-14T21:51:33ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:51:33Zurn:sha1:1f1a303c617057f149b4f0d748ee0a195484642ckrino: 0.0.3 — the plan as one block per file, wrapped, and -P2026-09-14T11:26:51ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T11:26:51Zurn:sha1:07c24054cab965800983ef40f53a05c2db131ede
Each file shows its steps, then the rule and the reason it matched, one
field per line; on a terminal every line wraps to its width with
continuation lines under their own column, and piped output is never
wrapped. Choosing per file shows the same block. -P / --no-pager prints
the plan without the pager. A duplicate's original is shown with ~.
krino: coloured output, and --no-color2026-09-14T09:05:13ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T09:05:13Zurn:sha1:adc3410395771609d2db5ee5ae2b9da71115c5ca
One palette type styles the plan table, warnings, headers, outcome counts,
prompt keys, undo's refused steps and krino log's (undone), from the
16-colour ANSI palette plus bold and faint only. Widths are measured on the
plain text, so columns line up; with colour off the output is unchanged.
--no-color works before or after any subcommand, as NO_COLOR does. The two
search-and-replace colourings are gone.
krino: planning — chains, placeholders, conflicts, JSON2026-09-12T10:58:14ZLukasz Kasprzaklukas@labunix.xyz2026-09-12T10:58:14Zurn:sha1:24a84671ace373ae331fa83a1ff484990f4dff0e