Great program, thank you John! I have converted about 5 years of my
companies' book records into ledger format and am playing currently
with the reports. Your intention to make application at high abstract
level is very interesting, but I am accountant, so probably my
language is more case-specific. Anyway, my findings so far:
1. the number of decimal points in --price-db file effects the
presentation of reports. Is there a way to have 2 dec. points in bal/
reg reports while keeping conversion rates with 4-6 dec. points?
2. The re-valuation of an commodity is done without regard to the
period limitation option, such as -e or -l = 'd<=[2008/12/01]'. I
think there should be at least option which change this behaviour.
3. I would wish to group totals (as with -P) on the basis of a
transaction's note - as it is already done for commodities and entry
numbers by means of 'substitution' (--code-as-payee, --comm-as-
payee) . As of grouping, it would be excellent to have option (as with
-l) to specify criteria for grouping using available value
expressions. Then it would be possible to devise elaborated notes
syntax for, say, tracking invoice payments, orders etc.
4. Argument to function U shall be surrounded by brackets - at least
in Linux. This differ from examples given in the manual.
5. It seems that there is no consistency in parameters to -b -e and -p
options. So,
ledger -b 2005/06/02 reg
does work, but
ledger -e 2005/06/03 reg
gives no output.
ledger -e 2005/10 reg
prints everything till the end of 2005, effectively disregarding
everything but the year.
The same story with -p:
ledger -p 2004 reg
works as expected, but with more precise argument, such as 2004/10
(the month is disregarded) or 2004/10/04 (no output at all) don't.
Of course, I can use -l 'd>=[2005/06/02]&d<=[2005/06/10]' , but it
would be nice to have -b -e option working.
Overall, the program is very inspiring. Thanks a lot.
