John, One thing I just noticed is that the forecaster with balance report does work if (and only if) the account is specified.
So --forecast "d<[2015-05-01]" bal goes out to the max but --forecast "d<[2015-05-01]" bal Assets:EOM works as expected. I thought this might help with the bug hunting.\ Greg On Sunday, May 25, 2014 2:34:42 AM UTC+8, John Wiegley wrote: > > >>>>> Greg Tucker-Kellogg <[email protected] <javascript:>> writes: > > > I'm having this exact same problem in Ledger 3.0.2-20140507, > > I'm not sure I ever tested the forecaster with the balance report! That > sounds like a bug to me. > > John > > On Sunday, July 18, 2010 4:34:02 AM UTC+8, spiffytech wrote: > > > When I run "ledger --forecast "d<[2011/01/01]" bal" I see expenses > and > > assets values in the hundreds of thousands of dollars. Since I'm a > > poor college student with $10k annual income, this is very wrong. > > Running ledger --forecast "d<[2011/01/01]" print" shows dates all > the > > way to December 2037, the largest date a signed int epoch timestamp > > can represent. Dividing the values from Balance by 27 (2037-2010) I > > get the $10k annual for both Expenses and Assets. > > > Using Register instead of Balance or Print stops at (nearly) the > > correct date. If I use "d<[2011/01/01]" I do get a transaction on > > January 1, 2011, which should not happen (< vs <=) > > > Am I doing something wrong, or is this a bug? I'm using Ledger > 2.6.2, > > though someone in #ledger reported what sounds like the same problem > > with 3.0. > > -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
