Simon Michael

Hi @mapreri.. the {} syntax is used by Ledger, but not hledger. https://hledger.org/journal.html#transaction-prices describes the syntax we currently support, and this seems related at https://hledger.org/faq.html#functional-differences : *"Ledger allows amounts to...

So, I think you can work around by just putting the {} last: ``` 2019-04-22 Foo ;Program: Bar ;Entity: Baz Accrued:Accounts Payable:Bar £-154.83 @ $1.29847 {=$1.29847} Expenses:Bar:A £154.83 @ $1.29847...

It's a good question. hledger so far ignores {} because I don't like that syntax - I find it overcomplicated and unnecessary. IIRC it does exactly what hledger's @ does...

@ony: thanks, very helpful examples. I will remember: "Ledger's `{}` is like `@` except it also generates capital gain/loss transactions". Do your manual entries get very tedious, eg if doing...

PS and what's the difference between `{AMT}` and `{=AMT}` ?

If I'm reading https://www.ledger-cli.org/3.0/doc/ledger3.html#Fixing-Lot-Prices right: - `{AMT}` is identical to `@ AMT`, and does not generate capital gains transactions - `{=AMT}` generates capital gains transactions See: > This transaction actually...

Related to #1029. I think we can consider this a sub-task of that.

But continuing this train of thought: As I understand it, Ledger has ~four~six syntaxes for specifying price in a transaction: `@`, `@@`, `{ }`, `{= }`, `{{ }}`, `{{= }}`....

This is seems interesting and possibly related, from https://www.cointracker.io/blog/new-irs-cryptocurrency-tax-guidance#specific-identification . I've added our terminology in brackets: > To successfully identify a specific unit [lot], information must include: > > -...

> So we need to either have a way to refer back to buy transaction, or to include cost basis into the sell transaction. And ledger's syntax `{= cost basis}'...