Simon Michael

I see, so it's useful enough to keep even as it stands. Then yes, we should figure out some way to warn loudly when it's triggered so users aren't baffled.

For the record: this was fixed in hledger 1.33.

Thanks for the report @aragaer. When you say "default commodity", I think of [`D`](https://hledger.org/hledger.html#default-commodity) and get confused; I am mentally translating to "no-symbol commodity". When someone uses the no-symbol commodity,...

And with hledger 1.21, I can reproduce. (A change in valuation in master seems.. unexpected and ominous..) ``` $ hledger-1.21 -f a.j bal assets:A -X 'B' --infer-value --debug=2 seeking A...

https://hledger.org/hledger.html#market-prices is the relevant doc. I note that it is quite hard to understand, and it isn't clear enough about how prices are prioritised. (Nor is the code in Hledger.Data.Valuation)....

PS when that's not what you want, the simple workaround is to add more P declarations. I imagine that heavy users of valuation would want daily market prices for all...

That's right - because we think that explicit declarations are more trustworthy / should be respected more than inferred price chains - which are after all a kind of convenience...

> Let's say I'm investing in several commodities and some of these are priced in US dollars and others are priced in Russian rubles. I want to have an overview...

I'm suggesting you would need daily P records for A->C as well. Perhaps this is hard to do in some cases ?

I reread the discussion, and still agree improvement is desirable here. I think I understand @ilya-konovalov's suggestion above, and I'd be happy to test it out if it existed. But...