Cool thanks, I'll check that out. For future reference for anyone who needs it.. I realized a few things after posting this. I had the same errors regarding unused pad entries when I ran 'bean-report main.bean print' I realized that my script and bean-report were both explicitly printing out the 'P' padded entries as well as the PAD directives. Also bean-report doesn't seem to print out the options.. so in short, this script probably would work if you go back and delete the PAD directives and add the options back.
But, I also realized I could accomplish what I wanted by implementing a plugin which transforms the transactions while reading/parsing the bean files. This actually is maybe preferable for me while I find out how I want to categorize everything as it seems to be non destructive.. it does not modify the bean files. I probably will reach a point I want to 'snapshot' everything and will then use bean-report to export a new bean file and then remove the plugin. On Tuesday, January 10, 2023 at 7:49:50 PM UTC-5 [email protected] wrote: > * Tim Legg <[email protected]> [2023-01-09 11:44]: > > 2008-04-25 * "#AMAZON.COM" "" > > Liabilities:BofA:PlatinumPlus -14.36 USD > > Expenses:Buckets:Unaccounted 14.36 USD > > > > I would like to script up something to go through all transactions where > > payee is ~ 'amazon' and change the Unaccounted to something else. > > I haven't looked at it yet but check out the emails about > "autobean.refactor" from October 2022 on this mailing list. > You should be able to fix up your file with autobean.refactor. > > -- > Martin Michlmayr > https://www.cyrius.com/ > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/beancount/a68f6d35-a5f0-4252-b581-1dc481ef4218n%40googlegroups.com.
