Scott Carpenter
2018-07-08 20:39:55 UTC
I'd proudly make a PR for this if I understood forks. See:
https://github.com/ledger/ledger/blob/next/doc/ledger3.texi#L2913
A transaction can have a ``state'': cleared, pending, or uncleared. The
default is uncleared. To mark a transaction cleared, put an asterisk
@samp{*} before the payee, after the date or code:
I believe this should be:
A transaction can have a ``state'': cleared, pending, or uncleared. The
default is uncleared. To mark a transaction cleared, put an asterisk
@samp{*} after the date, before the code or payee:
In testing, this isn't valid:
2018/07/08 (123) * payee name
https://github.com/ledger/ledger/blob/next/doc/ledger3.texi#L2913
A transaction can have a ``state'': cleared, pending, or uncleared. The
default is uncleared. To mark a transaction cleared, put an asterisk
@samp{*} before the payee, after the date or code:
I believe this should be:
A transaction can have a ``state'': cleared, pending, or uncleared. The
default is uncleared. To mark a transaction cleared, put an asterisk
@samp{*} after the date, before the code or payee:
In testing, this isn't valid:
2018/07/08 (123) * payee name
--
---
You received this message because you are subscribed to the Google Groups "Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ledger-cli+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
---
You received this message because you are subscribed to the Google Groups "Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ledger-cli+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.