1 files changed, 19 insertions, 5 deletions
diff --git a/man/krino-gui.1 b/man/krino-gui.1
index 1a883fa..67dbecb 100644
--- a/man/krino-gui.1
+++ b/man/krino-gui.1
@@ -43,10 +43,19 @@ Pick one of the directories
 .Pa krino.conf
 includes and press
 .Cm Scan .
+The box beside it filters the plan: type a few letters of a name or of a
+rule, in order, and only the files they appear in are listed - capitals and
+accents ignored, as a rule with
+.Ic (fold yes)
+would. While a filter is on,
+.Cm Select all
+checks what is on screen and the status line says how many checked files
+the filter is hiding.
 Scanning takes that directory's lock, which is held while the plan is
 shown, so nothing moves underneath it; a directory another krino is working
-in is reported rather than waited for. Each row is a file, what would
-happen to it and where, and the rule that decided. A file krino could not
+in is reported rather than waited for. Each row is a file, the action in capitals and coloured by what it does,
+where the file would go, and the rule that decided; a header names the
+columns. A file krino could not
 decide about - unreadable content, a failed duplicate check - is listed with
 the reason and cannot be selected.
 .Pp
@@ -65,7 +74,13 @@ the second only after a confirmation naming the file, as the
 .Cm t
 and
 .Cm d
-keys do in the terminal review.
+keys do in the terminal review;
+.Cm With checked
+does the same for every checked file at once. Either way the plan changes
+and nothing else: the files move when
+.Cm Apply
+is pressed, and closing the window with a plan still unapplied says so
+before it goes.
 .Pp
 .Cm Apply
 acts on the checked files and logs the rest as declined, exactly as
@@ -140,8 +155,7 @@ file may override; they are written to
 by the rules above: refused while the configuration would not load, the
 previous text kept as
 .Pa krino.conf.bak .
-The second is how this window behaves - the editor's font size, how tall the
-preview is, whether the configuration is coloured, whether the file behind a
+The second is how this window behaves - how tall the preview is, whether the configuration is coloured, whether the file behind a
 row is shown, and whether a scanned plan starts with every file checked. Those take effect as
 they are changed and are kept in
 .Pa gui.json ,