From cc2654b17b255f990ef0fa5078bb38d22a24a4a0 Mon Sep 17 00:00:00 2001
From: Simon Michael <simon@joyful.com>
Date: Sun, 15 Nov 2020 11:32:43 -0800
Subject: [PATCH] ;ui: notes (#1387)

---
 hledger-ui/Hledger/UI/Main.hs | 12 +++++-------
 1 file changed, 5 insertions(+), 7 deletions(-)

diff --git a/hledger-ui/Hledger/UI/Main.hs b/hledger-ui/Hledger/UI/Main.hs
index 8093b7f2b..bcce81887 100644
--- a/hledger-ui/Hledger/UI/Main.hs
+++ b/hledger-ui/Hledger/UI/Main.hs
@@ -101,13 +101,11 @@ runBrickUi uopts@UIOpts{cliopts_=copts@CliOpts{inputopts_=_iopts,reportspec_=rsp
     -- these can be combined to make the full query when needed, eg when
     -- hledger-ui screens are generating their data. (TODO)
 
-    -- hledger-ui provides special UI for controlling different parts of the query.
-    -- Eg the number/+/- keys for depth, the shift-up/down/left/right keys
-    -- for report period (date), the R and UPC keys for toggling realness
-    -- and status filters, and the / key for entering extra freeform query terms.
-    -- We generally store and show these parts separately, since it's cleaner
-    -- and less redundant/conflicting not to have date: and depth: terms in 
-    -- the query text users edit with the / key.
+    -- Some parts of the query are also kept separate for UI reasons.
+    -- hledger-ui provides special UI for controlling depth (number keys), 
+    -- the report period (shift arrow keys), realness/status filters (RUPC keys) etc.
+    -- There is also a freeform text area for extra query terms (/ key).
+    -- It's cleaner and less conflicting to keep the former out of the latter.
 
     uopts' = uopts{
       cliopts_=copts{