From 46767406edfd0d6de93f736463fec097df9e69e0 Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Thu, 28 Apr 2016 21:58:08 -0700 Subject: [PATCH] web: document how initial query works (fixes #314) --- hledger-web/doc/hledger-web.1.m4.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/hledger-web/doc/hledger-web.1.m4.md b/hledger-web/doc/hledger-web.1.m4.md index d185a05a8..8e6af02ef 100644 --- a/hledger-web/doc/hledger-web.1.m4.md +++ b/hledger-web/doc/hledger-web.1.m4.md @@ -78,10 +78,14 @@ Note there is no built-in access control, so you will need to hide hledger-web behind an authenticating proxy (such as apache or nginx) if you want to restrict who can see and add entries to your journal. -With journal and timeclock files (but not CSV files, currently) -the web app detects changes and will show the new data on the next request. -If a change makes the file unparseable, hledger-web will show an error -until the file has been fixed. +Command-line options and arguments may be used to set an initial +filter on the data. This is not shown in the web UI, but it will be +applied in addition to any search query entered there. + +With journal and timeclock files (but not CSV files, currently) the +web app detects changes made by other means and will show the new data +on the next request. If a change makes the file unparseable, +hledger-web will show an error until the file has been fixed. --- # disabled