Also, "balance" gives a different answer than "register" in that example.On Mar 22, 2024, at 3:29 PM, Bob Wilson wrote:I'm having the same issue.Example file:~ Monthly from 2024/02/15 Expenses:Rent $500.00 AssetsCommand:$ ledger -f test.dat --forecast "d<[2025]" register
I'm having the same issue.
Example file:
~ Monthly from 2024/02/15
Expenses:Rent $500.00
Assets
Command:
$ ledger -f test.dat --forecast "d<[2025]" register Expenses:Rent
24-Apr-01 Forecast transaction Expenses:Rent
$500.00 $500.00
Here's a demo of what I mean. Reading from "sample.dat" produces no output;
compare to "another.dat." (Data files attached.)
% ledger --version
Ledger 3.2.1-20200518, the command-line accounting tool
Copyright (c) 2003-2019, John Wiegley. All rights reserved.
This program is made available
> "A" == Alan writes:
A> Is it correct to glean from this that it doesn't work to give a "from" date
A> in a periodic transaction? I was trying to do so, but I was not able to
A> make it work.
I would definitely expect periodic transactions to accept date ranges.
Is it correct to glean from this that it doesn't work to give a "from" date
in a periodic transaction? I was trying to do so, but I was not able to
make it work.
On Tuesday, December 15, 2015 at 3:50:35 PM UTC-8 John Wiegley wrote:
> > Phil Gee writes:
>
> > As far as I understand
Just FYI, I've found a workaround: I focus less on the start and more on
the end of recurring transactions. With the following modification
everything seems to work fine. Note the "negative Expenses" for KFW which
compensate undue payments from january to march.
~ Monthly until 2016/12/01
