Well, we agree on the core functionality: being able to set an account
as 'no transactions'. We agree to disagree on the default setting of
such a beast.
As an olive branch, I'm perfectly willing to have to code something
like this in my guile file:
(setq gnc::default_no_transactions_in_parent_accounts 't)
;)
-derek
Dave Peticolas <[EMAIL PROTECTED]> writes:
>
> > names on the folders (parent accounts). It doesn't matter what the
> > organization is (or the account names), I still maintain that
> > transactions should only be in leaf nodes, and that 'folders' should
> > be the summation of it's children, but should never have transactions
> > itself. If it turns out that you do not have a leaf account to handle
> > the particular item, then maybe you should have a 'misc' account.
>
> I agree that being able to set an account as 'no transactions'
> would be useful, but I disagree that we should force this on
> all users. You may think that non-leaf accounts should never
> have transactions, but not everyone may agree with how you
> organize your accounts.
>
> Why should you force all your transactions into leaf accounts?
> For example, I have a 'gifts' account that has a sub-category of 'xmas',
> since I like to know how much I've spent on xmas gifts specifically.
> Of course, I buy other gifts, but rather than having a 'non-xmas' or
> 'misc' account it makes perfect sense, at least to me, to put those
> expenses in the non-leaf 'gifts'.
>
> dave
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL N1NWH
[EMAIL PROTECTED] PGP key available
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]