krino.git/internal/cond/eval.go, branch mainrule-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=main2026-09-17T12:17:54Za file's name is folded once, not once per name test2026-09-17T12:17:54ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T12:17:54Zurn:sha1:b66850cc8c584cc00bcd796eb3aa238bcf87394a
Folding is the expensive half of a name test on a name with diacritics,
and every name test of every rule folded the same name again: on Polish
names it was most of the matching work. The per-file facts memoise it,
which is where one file's work belongs - the object is per file and per
goroutine, so no lock.
4000 Polish names, twelve rules with name tests: 0.33s -> 0.13s
the 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.
a failed duplicate lookup is unknown, like unreadable content2026-09-15T20:10:44ZLukasz Kasprzaklukas@labunix.xyz2026-09-15T20:10:44Zurn:sha1:6b38d302daa54140e4e26ad903297a1bba0cbd41(matched) is unknown after an undecided rule, so a catch-all leaves an unreadable file alone2026-09-14T22:32:11ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:32:11Zurn:sha1:ccd6faf3d10da0669631fb3e3ba17a46b9e63a09content tests are three-valued: unknown when unreadable or read in part2026-09-14T21:39:37ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:39:37Zurn:sha1:c09020c2fb01da24d5befbed78ce3b73b5efbe4ccaptures keep the name's diacritics2026-09-14T21:34:51ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:34:51Zurn:sha1:3990586a85e91923c0a3ae1a1f0f61420db555acplan 9: content excludes fail closed; krino.conf excludes checked without directories2026-09-14T19:40:12ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T19:40:12Zurn:sha1:360591d6e18d8676a2f86185ed42f46852387f85krino: 0.0.5 — keyword cache, t and d in review2026-09-14T13:16:55ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T13:16:55Zurn:sha1:0b5d0eb92c5be2f0ddb2fa73990f31e5654e57fekrino: matching — scan, ignore, conditions, extraction, duplicates, explain, dry run2026-09-11T23:22:12ZLukasz Kasprzaklukas@labunix.xyz2026-09-11T23:22:12Zurn:sha1:3b36a48b7ce5a53a9366f3b31f94311f178e2553