I was struggling to understand what I needed to do to track these unrealized amounts in hledger until I understood what it needs to compute them. I’m sharing a summary here in case it helps others too:
2 Likes
Nice read! Investments are always a pain to record 
Unrelated feedback: is this your blog? If it is, the texts are a bit uncomfortably big to read on a big screen.
1 Like
Glad you enjoyed it!
Yup, this is my blog. The page’s font size scales with the width, but it has an upper bound to avoid ridiculous sizes. Could you tell me your screen size and resolution? I generally test on a 32″ 4K desktop screen, a 15″ 1080p laptop screen, and my phone’s 6″ 1080p screen.
I was using 1080p 15" laptop so no big difference. I think there's little need to touch font size settings because that should really set browser-level. I would personally advise against messing with the base font size. rem solves a lot of issues btw.
Recommend you read this: Accessible Font Sizing, Explained | CSS-Tricks
I’m surprised you’re having such a different experience, given that we appear to be using almost identical devices and I’m not aware of any modern browsers misbehaving with the relative units I use. Would it be possible for you to share a screenshot?
Thanks for the link, by the way. I’m familiar with the article. 
I use viewport units and rems, with clamp to prevent text being too large or too small (which is why I’d love to see a screenshot to figure out what’s going on). It would be nice to leave the base size up to the browser so I could just stop worrying about it, but that’s unfortunately a sub-par experience for most users on most devices.