krino.git/gui/internal/model/plan.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-17T12:19:23Zthe applying flag is atomic; its test waits instead of polling2026-09-17T12:19:23ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T12:19:23Zurn:sha1:40dbf18893c33bc40c8617d0f3e8de16ce2947e2
The race detector found my own new flag: Apply writes it on a worker
and Close reads it from the main loop. The test was polling a plain
field too, where the real window hears about the apply on the main
loop, which orders the writes.
Settings changes take effect, and keep this copy respects the plan2026-09-17T12:16:19ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T12:16:19Zurn:sha1:f74a02254ac15a84d38c9a254ead293ebaad2377
Five of the Settings window's controls - the sort order, the three
column toggles and the preview height - were read when it built its new
preferences but never connected to anything, so changing them did
nothing until some other control happened to fire, and then they all
landed at once out of nowhere. Every control is connected now.
The same closure composed a whole Prefs from its own widgets, which
wrote the remembered divider positions back as zeros: dragging the
panes to taste and then ticking any checkbox threw them away. A
settings change is now applied over the preferences as they are, by
model.Prefs.WithDisplay - which is where it can be tested, and is.
"Keep this copy, replace the other" wrote a Displaces straight into the
chain. internal/plan refuses to build two steps that displace one path,
because the second destroys what the first put there; the window went
round that code, so choosing it for two duplicates of one file left
both rows saying "done" with the first file in the Trash. It now
refuses the second, naming the file that has the place.
the window cannot pull the lock out from under a running apply2026-09-17T12:11:52ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T12:11:52Zurn:sha1:ed86f44a926fd1f0d438cbe5e2e10ad5b063db55
Close releases the directory lock and closes the log. The window could
reach it while an apply was still running - saving rules, saving
settings, adding a directory, or closing the window - and the engine
then went on moving files with the log shut underneath: a file moved
that no krino undo can see, the rest of the plan silently abandoned,
and the directory unlocked while krino was still working in it.
PlanTab and UndoTab refuse to close while their apply is in flight
(model.ErrApplying), the window's close request and reloadEngine honour
the refusal instead of ignoring it, and the tabs and Settings are greyed
out for the duration so a button that cannot work says so by being
unavailable rather than by an error afterwards.
The test starts an apply, calls Close from another goroutine while it
is in flight, and requires the refusal.
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.
gui: name the other copy of a duplicate, and offer to keep this one instead2026-09-17T08:15:45ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T08:15:45Zurn:sha1:a2cb20851499e9c00bd3bf642680a9ce3148cae8gui: size and age columns, column toggles, readable colours, a laid-out explanation2026-09-17T07:40:24ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T07:40:24Zurn:sha1:0e067e693609589d46f5aa6e161b95cc905987ccgui: coloured actions with headers, a filter over the plan, bulk trash or delete2026-09-16T22:51:15ZLukasz Kasprzaklukas@labunix.xyz2026-09-16T22:51:15Zurn:sha1:5418ba6bc5c653b6a99572c6ece6abbf57836c43gui: History and undo tab; each plan and undo is its own run2026-09-16T07:39:59ZLukasz Kasprzaklukas@labunix.xyz2026-09-16T07:39:59Zurn:sha1:6ef83d6bdfb6120f9e1fbd145e0bc463196103d1gui: row menu for trash or permanent delete; Apply frees the directory2026-09-16T07:28:32ZLukasz Kasprzaklukas@labunix.xyz2026-09-16T07:28:32Zurn:sha1:27eb6353030953e91a45b0104bd0567e53622090