|
|
|
| Description |
| A Transaction represents a single balanced entry in the ledger file. It
normally contains two or more balanced Postings.
|
|
| Synopsis |
|
|
|
| Documentation |
|
|
|
|
Show a ledger entry, formatted for the print command. ledger 2.x's
standard format looks like this:
yyyymmdd[ *][ CODE] description......... [ ; comment...............]
account name 1..................... ...$amount1[ ; comment...............]
account name 2..................... ..$-amount1[ ; comment...............]
pcodewidth = no limit -- 10 -- mimicking ledger layout.
pdescwidth = no limit -- 20 -- I don't remember what these mean,
pacctwidth = 35 minimum, no maximum -- they were important at the time.
pamtwidth = 11
pcommentwidth = no limit -- 22
|
|
|
|
|
|
|
|
|
| Show an account name, clipped to the given width if any, and
appropriately bracketed/parenthesised for the given posting type.
|
|
|
|
|
| Ensure that this entry is balanced, possibly auto-filling a missing
amount first. We can auto-fill if there is just one non-virtual
transaction without an amount. The auto-filled balance will be
converted to cost basis if possible. If the entry can not be balanced,
return an error message instead.
|
|
|
| Convert the primary date to either the actual or effective date.
|
|
|
| Ensure a transaction's postings refer back to it.
|
|
|
| Set a posting's parent transaction.
|
|
| Produced by Haddock version 2.6.0 |