It would probably be easier to implement this sort of thing in Python as a standalone script than to coerce ledger into doing it. Imagine a realistic ledger file that contained a "bucket" statement (or any other file level command or comment) in the down in the body of the file. Ledger allows it, and some people actually use it that way, but if you sorted the file where should the bucket statement end up? There was a long discussion about this last year or the year before when it came to how to handle file level comments and commands. It is the only case I can think of where ledgers flexibility actually gets in the way of a simple task.
On Fri, Aug 23, 2013 at 4:04 PM, Charles Merriam <[email protected]> wrote: > The print command is limited and requires a bit of eyeballing to catch the > errors. > > For example, this file: > > bucket out > > 2013/1/1 Foo > > in $0.01 > > > Has the correct register: > > $ ledger -f x.led register > > 13-Jan-01 Foo in $0.01 > $0.01 > > out $-0.01 > 0 > > > But the incorrect print statements: > > $ ledger -f x.led print > > 2013/01/01 Foo > > in $0.01 > > > It feels like a proper format command would be able to toss out an > idempotent register with "-S date" for the sorting. Idempotent is the fancy > way of saying running the command against its own output would still > reproduce the output. > > > -- > > --- > 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/groups/opt_out. -- Craig, Corona De Tucson, AZ enderw88.wordpress.com -- --- 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/groups/opt_out.
