<https://lh4.googleusercontent.com/-CbUeVGTrXdc/VDzGYhPpVII/AAAAAAAAC_4/h8PvsknH50I/s1600/Screenshot%2Bfrom%2B2014-10-14%2B10%3A42%3A42.png>
Thanks Simon! For now, I've decided to do the following: - I'll be entering and viewing my receipts and other such things in a dedicated .org file to leverage tree structure and tables and the capture/template capabilities. Something like the attached picture. - A simple script would then replace a couple of substrings to make it a valid ledger file, and I could probably get emacs to sync the files each time the org one is saved - So when I need a ledger report, I run ledger against ledger file, and when I need to quickly input or review something, I run emacs - Whenever something breaks out of that primitive setup, it goes to a special.ledger file with proper ledger syntax and it then gets included Did a little testing, looks nice so far. -- --- 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.
