After trying to fight to have a reverse chronological order setup, I ceded after realizing I'm going to be fighting how beancount ingest outputs data - namely the order of 'entries' returned from the extract method in an Importer is always going to be re-ordered in chronological order. Seems to be better to go for for convention over configuration.
As far as re-ordering my existing ledger back into chronlogical order, you can just use bean-query 'print' to do this: $ bean-query myLedger.beancount print > myLedger-chronological.beancount On Saturday, November 25, 2017 at 1:34:51 PM UTC-8, Vivek Gani wrote: > > Hi! I've been learning beancount and have been really impressed with the > thought and structure that's gone into it. I'm a bit afraid of going into a > bikeshedding argument here, but is there any issue with using beancount in > reverse chronological order (newest first)? So far I haven't seen any > argument against it, though all the examples skew towards a normal > chronological order - is the rationale for that method so it's easier to > 'append' new transactions? > > Cheers, > Vivek > -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/da1c17b5-aec1-47c7-8ebd-cb445933f77a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
