You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a potentially surprising behaviour noted in hledger manual > More valuation examples, circa version 1.31.
Here, A's value in B is 0.5B, and a valued print report shows it as expected:
P 2023-01-01 A 0.5B
2023-01-01
a 1A
b
$ hledger-1.31 print -X B
2023-01-01
a 0.5B
b -0.5B
Here is the same transaction, but this time the rate is inferred
by reversing the declared B to A price, and there's no B amount
written in the journal from which to infer a display precision,
so B is displayed with the default style (symbol on the left)
and precision (0 decimal digits).
(Also, because the displayed amount looks like zero, no minus sign
is displayed, and before 1.30 the symbol was not displayed either.)
P 2023-01-01 B 2A
2023-01-01
a 1A
b
$ hledger-1.31 print -X B
2023-01-01
a B0
b B0
Other reports are similarly affected:
$ hledger-1.31 bal -E -X B
0 a
0 b
--------------------
0
The text was updated successfully, but these errors were encountered:
…ngeddon)
`print -V` and other value reports now tend to show valued amounts
with the precision of the market price that was used to calculate them
(showing all significant decimal digits).
And new tests have been added describing and explaining various
style/precision behaviours in print cost/value reports.
… precisiongeddon)
Cost/value conversion now applies the standard display style, and
sets the display precision equal to the internal decimal precision
(or 8 if the decimal appears to be infinite).
This means value reports and especially `print -V` now show amounts
with more accurate and standard style and precision.
New tests have been added describing and explaining various
style/precision behaviours in print cost/value reports.
This is a potentially surprising behaviour noted in hledger manual > More valuation examples, circa version 1.31.
Here, A's value in B is 0.5B, and a valued print report shows it as expected:
Here is the same transaction, but this time the rate is inferred
by reversing the declared B to A price, and there's no B amount
written in the journal from which to infer a display precision,
so B is displayed with the default style (symbol on the left)
and precision (0 decimal digits).
(Also, because the displayed amount looks like zero, no minus sign
is displayed, and before 1.30 the symbol was not displayed either.)
Other reports are similarly affected:
The text was updated successfully, but these errors were encountered: