Simon Michael

Nice! I often do the same to prototype a feature. On the upside, you cleaned up your data a bit..

The next level of robustness would be a hledger script or two, which can use hledger's parsers, and mimic the code in Register.hs/Print.hs. (`hledger-register-pretty-tsv.hs`, `hledger-print-pretty-tsv` or some such..)

(I'll try out your script. PS, nice https://github.com/schoettl/hledger-contrib repo, we should link it somewhere.)

That bash script looks very nice. I have been writing many recently in almost exactly that style, but I see some new things to learn from yours. I'm not seeing...

PPS: ``` -s a single date, i.e. "2021-11-19" instead of "2021-11-19=2021-11-20". ``` Yet another case of secondary dates getting in the way. I'm starting to really detest this feature!

> But hledger doesn't has a parser for register output, has it? No, I meant the script can use hledger-lib to parse files just as the builtin commands do.

"Surprising developments in old behaviour, as a consequence of #931: now that print shows amounts with all of their decimal places, we had better balance transactions using all of those...

May need a bit more tweaking. It's visibly more picky about unit transaction prices (@), sometimes requiring them to be more precise than previously.

PS here's the original motivation for this: after #931, I hoped that print's output would always be parseable, but sometimes it still wasn't, because transaction balancing was still influenced by...

As mentioned, the new balancing is more picky, requiring more decimals in unit prices for certain transactions (where you have more decimals than usual, eg from investment transactions). It's arguably...