gui: aligned columns, theme colours, a second layout, and a scan-selection setting

1 files changed, 8 insertions, 5 deletions

diff --git a/man/krino-gui.1 b/man/krino-gui.1
index 67dbecb..1cfb76d 100644
--- a/man/krino-gui.1
+++ b/man/krino-gui.1
@@ -53,9 +53,10 @@ 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, 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
+in is reported rather than waited for. Each row is a file, the action in capitals and coloured by what it does -
+the colours are the running GTK theme's own accent, warning and error - where
+the file would go, and the rule that decided; a header names the columns,
+and an outcome column appears once a plan has been applied. A file krino could not
 decide about - unreadable content, a failed duplicate check - is listed with
 the reason and cannot be selected.
 .Pp
@@ -155,8 +156,10 @@ 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 - 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
+The second is how this window behaves - how the tab is arranged (the file
+list beside the explanation, or above it with the preview to its side), how
+tall the preview is, whether a scan starts with every file checked or none, whether the configuration is coloured, and whether the file behind a
+row is shown. Those take effect as
 they are changed and are kept in
 .Pa gui.json ,
 which krino itself never reads.