On 2023-01-27, at 22:39, John Wiegley <[email protected]> wrote:
>>>>>> "MB" == Marcin Borkowski <[email protected]> writes: > >> 1. Why is there no "budget transaction" for groceries for 2022-01-01? > > Use this: > > ~ Daily from 2022-01-01 Great, thanks! >> 2. I would assume that after these three days my "books" budget should >> allow me to spend 155 PLN more on books and my "food" budget would >> be short of 30 PLN. Yet I can see neither of these amounts in the >> report. How to make Ledger compute them? > > Did you try the "budget" report? No, it looks /very/ good! I did some experiments, and here is what I came up with. Can you confirm that I guessed correctly? 1. I can do ~ Daily from 2022-01-01 to 2023-01-01 ~ Daily from 2023-01-01 (the intervals are closed-open, like with -b/-e). Right? 2. The --invert option does nothing for the `budget` report. Correct? 3. If I don't provide -b, the default for the budget seems to be what was in `~ Daily from`, but the transactions from before that date also count towards the actual expenses. That probably means that I should /always/ provide -b to the `budget` report. Is that right? 4. If I don't provide -e, the default (for the `budget` report) is --current. Is that correct? 5. If I don't provide `from` in `~ Daily`, the default seems to be the date if the /first/ transaction on a given account. Right? 6. (Almost) last but not least -- the `budget` report gives me a table with 5 columns: - actual expenses - budgeted expenses - the difference (negative means I spent less than the budget -- a bit counterintuitive, but makes sense given the order of the previous two) - what percentage of the budget was spent - name of the account Using classical spreadsheet column names: C = A - B and D = A/B (as percentage). Do I guess correctly? If so, this means that the web app I wrote to present this exact information is mostly irrelevant. %-P Still, it draws a nice chart which is accessible from a smartphone. I have a post-commit hook which scp's the file to my VPS, and the web app there serves the chart - that's a very useful arrangement I plan to blog about one day. Now, my final question is this. Much of what we discuss here is apparently undocumented in the Ledger manual. My book is my book, and it contains examples and such, but I think it is fair to have these options at least mentioned in the manual. I have just fetched the ledger repo, and I can see that the last commit in `ledger/doc/ledger3.texi` was 7 years ago... Would you accept a PR with a small manual update? (One minor issue with that idea is that I don't speak texinfo, so you'd have to check every my edit very carefully.) Best, -- Marcin Borkowski http://mbork.pl -- --- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/ledger-cli/877cx4ef47.fsf%40mbork.pl.
