> "r" == ra writes:
r> What workaround using ledger-cli would you suggest for forecasting future
r> budgets?
I don't know of anything off hand, but perhaps some of the other users here
might have suggestions?
John
--
---
You received this message because you are subscribed to the Googl
Hi John
Thank you.
What workaround using ledger-cli would you suggest for forecasting future
budgets?
Am Donnerstag, 19. April 2018 10:52:09 UTC+2 schrieb John Wiegley:
>
> > "r" == ra > writes:
>
> r> Can you confirm future forecasting as original poster intends is *not*
> r> working?
> "r" == ra writes:
r> Can you confirm future forecasting as original poster intends is *not*
r> working?
I'm guessing it doesn't work, but I don't remember the original issue well
enough anymore. Looking back at the message history, it would require some
time to re-familiarize myself.
Joh
Hi John
Can you confirm future forecasting as original poster intends is *not*
working?
Thank you
P.S. Thank you for your marvelous work
Am Sonntag, 28. Januar 2018 20:34:04 UTC+1 schrieb John Wiegley:
>
> > "CD" == Colin Dean > writes:
>
> CD> I have not yet arrived at a solution. I'd we
Same problem here, though I would like to countercheck your workaround
report "within those dates". Could you please provide this report?
Am Sonntag, 18. Februar 2018 12:22:45 UTC+1 schrieb tydn:
>
> In other words, you can see those periodic transactions in your
> forecasting, only if you gener
In other words, you can see those periodic transactions in your
forecasting, only if you generate the report within those dates. Can anyone
confirm?
--
---
You received this message because you are subscribed to the Google Groups
"Ledger" group.
To unsubscribe from this group and stop receiv
I have the same problem. After some experimenting it seems the "from" and
"until" dates refer to the actual current date, which seems unexpected
behavior for forecasting.
--
---
You received this message because you are subscribed to the Google Groups
"Ledger" group.
To unsubscribe from this
> "CD" == Colin Dean writes:
CD> I have not yet arrived at a solution. I'd welcome input!
Hi Colin,
So, in an unexpected turn of events while writing a Haskell time tracking
program, I ended up inventing a new kind of budgeting algorithm that is both
simpler and more power than what is curr
>
> > What's up here? Did I find a bug or am I doing something wrong?
>
> Did you find out more on this one? Would be interesting to know the
> solution here.
I have not yet arrived at a solution. I'd welcome input!
--
---
You received this message because you are subscribed to the Google
On 08.12.17,11:54, Colin Dean wrote:
> I'm trying to capture budgets that change over time. It may start with
> simply a ~ Monthly transaction but, over time, I want to "retire" old
> budget amounts as well as document future budget changes, e.g. stepped
> payment plans on rent, student loans, e
I'm trying to capture budgets that change over time. It may start with
simply a ~ Monthly transaction but, over time, I want to "retire" old
budget amounts as well as document future budget changes, e.g. stepped
payment plans on rent, student loans, etc.
I had something like this in test.ledger
11 matches
Mail list logo
