On Wed, Jul 23, 2014 at 4:28 PM, Walker Pendleton <[email protected]> wrote:
> On Tue, Jul 22, 2014 at 7:38 PM, Dave Wells <[email protected]> wrote: > > OK, thanks. The problem with the approach you suggest, though, is > > that I still want to set actual categories > > (e.g. Expenses:Shopping:Software) on all purchases, I just don't > > necessarily want a separate budget for each category. I suppose I > > can have sub-accounts of Expenses:Misc, but then I lose the > > flexibility of later introducing a budget for a previously > > miscellaneous account. Plus "Misc" isn't really intrinsic to the > > transaction, but an artifact of the budget. > > I budget this way, as I too have also found putting balances in > accounts that have children to be confusing and unhelpful. > I guess that's a choice. I like the idea of creating a strict mode, e.g., using a Beancount plugin that one can load in order to turn on "strict" more, that would simply look for transactions with postings to accounts that have children and issue corresponding errors. If you like to be strict and avoid this, you would insert this in your input file: option "plugin" "beancount.plugins.empty_parents" or something like that. -- --- 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.
