krino.git - rule-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 window

	Commit message (Collapse)	Author	Age	Files	Lines
*	the module path is git.labunix.xyz/krino	Lukasz Kasprzak	2 days	1	-3/+3
\| \| \| \| \| \| \| \| \| \| \|	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 written	Lukasz Kasprzak	2 days	1	-5/+5
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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 ↵	Lukasz Kasprzak	5 days	1	-1/+7
\| \| \| \|	a column
*	output: wrap by terminal columns, names cannot fake step lines, -v lists ↵	Lukasz Kasprzak	5 days	1	-2/+53
\| \| \| \|	unscanned destinations
*	krino: 0.0.3 — the plan as one block per file, wrapped, and -Pv0.0.3	Lukasz Kasprzak	5 days	1	-25/+119
\| \| \| \| \| \| \| \|	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-color	Lukasz Kasprzak	5 days	1	-4/+4
\| \| \| \| \| \| \| \| \|	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, JSON	Lukasz Kasprzak	7 days	1	-0/+283