| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
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 ~.
|
| |
|
|
|
|
|
| |
Lukasz, 2026-09-14: colour the output for ease of reading, with an option of
no colour. Section 8.2 now lists what is styled, from the 16-colour ANSI palette
plus bold and faint only, so the terminal theme decides the look; section 11
adds --no-color; section 15 adds the colour tests.
|
| |
|
|
|
|
|
|
|
| |
A rule combining (duplicate) with a delete action is refused at load, and a
file that is a duplicate under any duplicate scope its directory uses gets no
delete step from any rule: the plan shows it skipped and the chain continues.
A failed duplicate check blocks the delete too. Tests cover (matched), another
rule's own condition, a test evaluation skipped, two scopes and a failed
check, each checking every copy is still on disk.
|
| |
|
|
|
|
|
|
|
| |
Lukasz, 2026-09-14: leave deleting duplicates to the user or jdupes. Section
5.5 now forbids a delete action in any rule using (duplicate), and skips any
delete step for a file that is a duplicate under a scope its directory uses,
which closes the (matched) and other-rule routes. Two scopes that elect
different originals can then only move copies aside, never delete them. The
consequences land in 4.5, 7.1, the 8.2 example, 15 and 17.
|
| |
|
|
|
|
|
|
|
| |
README, changelog
Also: undo removes the directories its run created; a hardlink is never a
duplicate of its own other name; a flag written before "undo" is honoured;
--version prints no leading v. Duplicate conditions with different scopes
not sharing an original is documented as a known limitation.
|
| |
|
|
|
|
|
|
|
|
| |
Lukasz: "no performance goal". Section 13s "under 2 s on a 4-core laptop" is
replaced with the decision and its evidence, so it is not reinstated later:
measured throughput is dominated by the external extractors, not by krino. A
real folder of 265 files with 164 needing pdftotext at roughly 80 ms each takes
12-17 s; a synthetic 4405-file tree needing no extraction takes 1.09 s. A single
threshold would describe popplers speed and the shape of one folder. The
measurement is still reported in the release notes; nothing is promised.
|
| | |
|
| | |
|
| |
|
|
| |
explain, dry run
|
| |
|
