I understand. This was a bit of a pain point during the data conversion but at least the nice people here pointed it out. The PWA I use for data entry on my phone will likely continue to spit out the numbers with the default JS precision (and I like it that way, maybe I'm just used to it) so I'm sure the new records will be affected. And I'd rather keep the minimum viable numbers than append an explicit ".00" to any number in the ledger. BTW, I've added the beancount format to Cashier export. Just need to complete the sync, to be able to initialize the app from an existing book using bean-query.
On Fri, 23 May 2025, 23:30 Martin Blais, <[email protected]> wrote: > This has been the very, very top annoyance and bug report. I think I'm > diving in this time to fix it. > It's not that crazy hard but it's not trivially simple either without > ripping out a bunch of currently working stuff - tolerance inference mostly > works and if I remove it it would force everyone to have to add options for > things to continue working as they were - so I have to keep inference > working underneath. > It'll involve some documentation and some new/renamed configuration > options, but I think I have a way to keep it simple. > > > On Fri, May 23, 2025 at 4:49 PM 'Alen Šiljak' via Beancount < > [email protected]> wrote: > >> This is great to see! Thanks a lot for your efforts. >> >> On Thursday, 22 May 2025 at 11:30:17 pm UTC+2 [email protected] wrote: >> >>> I've implemented a new option for the display precision: >>> >>> https://github.com/beancount/beancount/commit/89a0e48df40f7c95c7ec29f2f6028a5b3d16212b >>> >>> https://github.com/beancount/beancount/commit/9e148b76216982ec938d84726f12dab48b3a2444 >>> >>> [image: image.png] >>> >>> I vibecoded the tests. >>> (I should do one for tolerance as well) >>> >>> >>> >>> >>> >>> >>> On Thu, May 22, 2025 at 11:21 AM Martin Blais <[email protected]> wrote: >>> >>>> bean-report is deprecated. >>>> AFAIR its precision was a distinct implementation from beanquery. >>>> Use beanquery. >>>> >>>> Use 3.0 instead of 3 you should be alright. >>>> Long term fix is to add an option to fix the precision form explicit >>>> declarations. >>>> >>>> >>>> >>>> On Wed, May 21, 2025 at 8:51 AM Dan Andersson <[email protected]> >>>> wrote: >>>> >>>>> Version 2.3.6. Running bean-report file.beancount balances on this: >>>>> >>>>> --- >>>>> 2022-12-05 open Assets:Stock >>>>> 2022-12-05 open Assets:Cash >>>>> >>>>> 2022-12-05 * "" >>>>> Assets:Stock 3 STOCK { 50 USD } >>>>> Assets:Cash -150 USD >>>>> >>>>> 2022-12-06 * "" >>>>> Assets:Stock -3 STOCK { 50 USD } >>>>> Assets:Cash 150 USD >>>>> >>>>> ; Buy 0.5 shares (broker supports fractional shares). >>>>> 2022-12-07 * "" >>>>> Assets:Stock 0.5 STOCK { 60 USD } >>>>> Assets:Cash -30 USD >>>>> --- >>>>> >>>>> gives an unexpected result: >>>>> >>>>> --- >>>>> Assets:Cash -30 USD >>>>> Assets:Stock 0 STOCK >>>>> --- >>>>> >>>>> (Shouldn't the user be able to confidently specify 0.5 STOCK, without >>>>> worrying that Beancount will just ignore it only because prior events had >>>>> less precision?) >>>>> >>>>> BTW, commenting out the middle directive: >>>>> >>>>> --- >>>>> 2022-12-05 open Assets:Stock >>>>> 2022-12-05 open Assets:Cash >>>>> >>>>> 2022-12-05 * "" >>>>> Assets:Stock 3 STOCK { 50 USD } >>>>> Assets:Cash -150 USD >>>>> >>>>> ; 2022-12-06 * "" >>>>> ; Assets:Stock -3 STOCK { 50 USD } >>>>> ; Assets:Cash 150 USD >>>>> >>>>> ; Buy 0.5 shares (broker supports fractional shares). >>>>> 2022-12-07 * "" >>>>> Assets:Stock 0.5 STOCK { 60 USD } >>>>> Assets:Cash -30 USD >>>>> --- >>>>> >>>>> and the 0.5 STOCK is no longer ignored: >>>>> >>>>> --- >>>>> Assets:Cash -180 USD >>>>> Assets:Stock 3.5 STOCK >>>>> --- >>>>> >>>>> -- >>>>> 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/7c891999-aad1-4c73-a134-704f615a2a4en%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/beancount/7c891999-aad1-4c73-a134-704f615a2a4en%40googlegroups.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/69ee815a-03d2-476f-a646-a8ec974d9233n%40googlegroups.com >> <https://groups.google.com/d/msgid/beancount/69ee815a-03d2-476f-a646-a8ec974d9233n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Beancount" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beancount/3LQ8iCy_z-g/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/beancount/CAK21%2BhOj6Y11GRML6kaLKqVZoT0SRC1MVGQr2gjqmkXb3Wez1Q%40mail.gmail.com > <https://groups.google.com/d/msgid/beancount/CAK21%2BhOj6Y11GRML6kaLKqVZoT0SRC1MVGQr2gjqmkXb3Wez1Q%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/CAED51T7SW1hDeQ2VBGUtz_T-pCGt_1dQFEhBKBr__%2B5jq1AH6g%40mail.gmail.com.
