Ditto - adding to the already present comments. I use a handful of the *builtin* plugins that you've already talked about being covered (check_commodity, coherent_cost, implicit_prices), some *fava* ones (tag_discovered_documents, link_documents), *autobean* (stock_split, narration), *redstreet* (zerosum, effective_date), and then a few *home-baked* plugins that just work well for my workflow (controlling tags and metadata from a master list, promoting a posting level metadata "tag" to a transaction level proper tag, and adding descriptions to matched zerosum transactions so I know which account the transfer is with).
I think I could do without my home-baked ones, but they are *fun* to just mess with. They open a whole world of possibility with beancount, and I imagine have helped spur adoption of the tool. To call out zerosum specifically, I use it with my institution imports where the debit and credit fall on different days. I'd be pretty sad to lose that one in particular. Excited to see limabean with such active development and will be sure to try it soon! On Wednesday, March 4, 2026 at 8:12:04 AM UTC-5 [email protected] wrote: > TL;DR but did you see this? > > https://docs.google.com/document/d/1qPdNXaz5zuDQ8M9uoZFyyFis7hA0G55BEfhWhrVBsfc/edit?tab=t.0#heading=h.axs6y16wohk9 > > On Mon, Mar 2, 2026 at 5:00 PM 'Simon Guest' via Beancount < > [email protected]> wrote: > >> A limabean issue <https://github.com/tesujimath/limabean/issues/46> has >> raised a question about how plugins should work, and highlighted that my >> approach in limabean differs from the historical behaviour >> <https://beancount.github.io/docs/beancount_scripting_plugins.html#load-pipeline> >> . >> >> It comes down to, what are plugins for, actually? >> >> The specific plugin which initiated the discussion was zerosum >> <https://github.com/redstreet/beancount_reds_plugins/tree/main/beancount_reds_plugins/zerosum>. >> >> Currently it is not possible to run such a plugin in limabean because >> limabean plugins run after the booking process has completed, and until >> such a plugin has run the beanfile is invalid. >> >> My first instinct was, well, fix the beanfile! That particular plugin >> seems to be a mitigation for an import process which doesn't pair >> transactions between accounts, in contrast to limabean-harvest >> <https://github.com/tesujimath/limabean-harvest> for example, which >> handles transaction pairing across accounts on import >> <https://github.com/tesujimath/limabean-harvest/blob/main/clj/doc/10-features.md#transaction-pairing> >> . >> >> My proposed mitigation for what I am calling such breakage (sorry) in >> beanfiles would be to run user-defined functions over the beanfile whose >> final output would be a fixed-up beanfile which passes validation. >> >> I understand there is legacy behaviour here. But the vNext document has >> some interesting plugin-related discussion >> <https://beancount.github.io/docs/beancount_v3.html#intermediate-parsed-data-vs-final-list-of-directives>, >> >> which says: >> >> >> >> *Furthermore, there may be two types of plugins: a plugin that runs on >> the uninterpolated, unbooked output of the parser, and a plugin that runs >> on the resolved and booked stream. This would allow more creative use of >> partial input that might be invalid under the limitations of interpolation >> and booking.Updates:- We could convert the plugin system to one that runs >> at booking/interpolation time.* >> >> I am interested to understand other scenarios which would illuminate >> design choices here. >> >> -- >> > 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 visit >> https://groups.google.com/d/msgid/beancount/CAFhGSbuECVFGk_mrSuhE9u-LWiS-%2BzTs0EjTsHt5vTOCKg8YQw%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/beancount/CAFhGSbuECVFGk_mrSuhE9u-LWiS-%2BzTs0EjTsHt5vTOCKg8YQw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 visit https://groups.google.com/d/msgid/beancount/6daec2d4-a470-4d33-b106-b6e77c49b0e8n%40googlegroups.com.
