And BTW, the only reason I say "more or less" is because the parser will attach meta-data that contains the original line number to the directives; but none of the processing makes use of it, other than the "bean-doctor context" command, which uses it for finding the closest transaction from a particular line number.
On Sun, Nov 26, 2017 at 10:32 AM, Martin Blais <[email protected]> wrote: > About your prior question: Beancount completely disregards order. It is > more or less thrown away; all the directives are sorted by date for > processing. > > > On Sat, Nov 25, 2017 at 5:45 PM, Vivek Gani <[email protected]> wrote: > >> After trying to fight to have a reverse chronological order setup, >> > > What difficulties did you encounter? There should have been none. > Beancount throws away ordering (on purpose). > > > >> 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. >> > > That's trivial to change; there's a command-line option to output the > entries in reverse order. > See here: > https://bitbucket.org/blais/beancount/src/6292d31f5d14b4bcb282847241b82d > 9505589e0e/beancount/ingest/extract.py?at=default& > fileviewer=file-view-default#extract.py-190 > > > > >> >> 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/ms >> gid/beancount/da1c17b5-aec1-47c7-8ebd-cb445933f77a%40googlegroups.com >> <https://groups.google.com/d/msgid/beancount/da1c17b5-aec1-47c7-8ebd-cb445933f77a%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/CAK21%2BhMsbiE0tmTt548-i4PBBG%2BctdxU8kBB2g2vDfqAfq4wNQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
