Was wondering the same thing. Does anyone have any insights? If not, is there more user control over decimal places intended in v3?
On Saturday, December 10, 2022 at 3:50:01 PM UTC-5 [email protected] wrote: > I populated price data with bean-price which is causing fava to show a lot > of decimal places (~14). > > This happens regardless if the price data is in my main beancount file or > a secondary one. > > I read through everything I could find but what I've gathered is that > tolerances and precisions are inferred first and foremost (before > considering any options). Is there a recommendation here? Is the only path > forward to modify all the price data to only have two decimal places? I've > been looking mostly in these place: > - > https://docs.google.com/document/d/1lgHxUUEY-UVEgoF6cupz2f_7v7vEF7fiJyiSlYYlhOo/edit# > > <https://docs.google.com/document/d/1lgHxUUEY-UVEgoF6cupz2f_7v7vEF7fiJyiSlYYlhOo/edit> > - https://groups.google.com/g/beancount/c/tsYAf02DSq4/m/ZaQrFQ0xAgAJ > - > https://github.com/beancount/beancount/blob/master/beancount/parser/options.py > > Colton > -- 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/75688333-c0a0-40b9-a11a-bc05f214873an%40googlegroups.com.
