Thanks for the replies and the insights. It's pretty much as I thought. The direction I'm taking with limabean is very much about user experience rather than performance, and it certainly does not position itself for that rapid update cycle use case (at least not for now).
There does seem to be a need for a solution to the update/reprocess cycle that's better than reading the whole input file from scratch though. That seems like a painful process indeed. This kind of partial update is precisely what LSP servers address (and indeed, there is an LSP server for Beancount). Does the LSP approach fall short in other ways? -------- Original Message -------- On Friday, 03/20/26 at 12:17 Martin Michlmayr <[email protected]> wrote: * 'Simon Guest' via Beancount <[email protected]> [2026-03-19 05:36]: > If you load your beanfile and run the plugins and booking algorithm > so all the context is sitting in the engine while you make a number > of queries, why does it matter if it takes a couple of seconds to be > ready to answer queries? Because I edit my books all the time, and so the cache needs to be rebuilt. Imagine running bean-check after each edit and it takes (say) 5 seconds. -- 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 visit https://groups.google.com/d/msgid/beancount/20260319231724.GA196249%40panya.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 visit https://groups.google.com/d/msgid/beancount/IQcEjBrPEWdbUpAqEl5Hw_0dHDNt3KwjAoSknSyKr43ohs8dDMAkbKSn6B5eD52uD1t4f47MaRHgK2BYAhdGalXaYnDfzeOoRaNw7cRl4Xg%3D%40tesujimath.org.
