| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
This outputs the pricing relationship of commodities in your data file,
as of DATE (optional), using the DOT language. If you have graphviz
installed, it can be viewed quite simply using:
ledger pricemap | dotty -
Each relationship in the graph shows the conversion factor to exchange
one commodity for another, and the date at which this factor was
determined.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The --group-by option allows for most reports to be split up into
sections based on the varying value of EXPR. For example, to see
register subtotals by payee, use:
ledger reg --group-by=payee -s
This works for separated balances too:
ledger bal --group-by=payee
Another interesting possibility is seeing a register of all the accounts
affected by a related account:
ledger reg -r --group-by=payee
The option --group-title-format can be used to add a separator bar to
the group titles. The option --no-titles can be used to drop titles
altogether.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The purpose of this option is to add special "<Rounding>" postings, to
ensure that a regiter's running total is *always* the sum of its
postings. Within --rounding, these adjustment postings are missing,
which was the behavior in Ledger 2.x. It can be orders of magnitude
slower to turn it on for large reports with many commodities.
|
|
|
|
| |
Fixes 3AAB00ED-9904-4380-8988-16506B0AFE08
|
|
|
|
|
|
|
|
| |
This is useful for making sure that the column containing the results of
--prepend-format is a consistent width throughout the report (including
those lines where it is not applied).
Fixes 64F9D913-75E1-4830-A3D9-29B72442E68B
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These three reports simply dump an unordered list (with the exception of
payees) shows all accounts, payees, and commodities represented in a
given report. This can be used to easily generate per-entity report,
for example:
ledger payees | \
while read payee; do \
echo ; echo $payee ; \
ledger reg payee "$payee" ; \
done
|
|
|
|
| |
This is really for debugging more than anything else.
|
|
|
|
|
|
|
|
| |
The usages are:
--meta=<TAG> prepend value of TAG before every line
--meta-width=<NUM> force the meta column to be NUM wide
--meta=<TAG>:<NUM> shortcut that also applies --meta-width
|
|
|
|
|
| |
There ended up being too many corner cases for the generalized formatter
to handle.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This is equivalent to the following:
--account='"TAG:" + tag(/TAG/)'
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
These options allow the user to specify what accounts names should be
used for these two types of accounts. They are optional, and default
to:
--unrealized-gains "Equity:Unrealized Gains"
--unrealized-losses "Equity:Unrealized Losses"
These are intended to be set in one's ~/.ledgerrc file.
|
| |
|
|
|
|
|
|
| |
When this option is on, then in balance report which show market values,
any gains or losses in value will be balanced into a pair of accounts
called Equity:Unrealized Gains and Equity:Unrealized Losses.
|
|
|
|
|
| |
This happens after running through all the post handlers, before running
any of the account handlers.
|
|
|
|
| |
It's always possible the user only specified a display predicate.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
They are:
to_boolean
to_int
to_datetime
to_date
to_amount
to_balance
to_string
to_mask
to_sequence
|
|
|
|
|
|
|
| |
This lets you do things like store a date as the value of a tag, then
run:
ledger --date='has_tag("Foo") ? to_date(tag("Foo")) : date' reg
|
| |
|
|
|
|
|
|
|
|
| |
This lets you, for example, debug registers that cull data from many
different sources, without having to change the basic formatting
string. You can locate each posting's location with this:
ledger reg --prepend-format='%-25(filename + ":" + beg_line)'
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This allows for correct searching of UTF-8 encoded strings, such as
lower-case versions of Russian words to find mixed-case words.
|
|
|
|
|
|
|
| |
This fits better with the --amount and --total options, which both
change the amount and total used for calculation. Same with --account:
it happens after filtering, but before calculation so that balance
reports look as you'd expect.
|
|
|
|
|
| |
This is used for accessing an account's current total within one's
Ledger file.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The different namespaces are:
Function Value expression functions, which receive a "context"
Option Command-line options
Precommand Commands which are invoked before reading the journal
Command Commands which are invoked after reading the journal
Directive Directives that occur at column 0 in a data file
This greatly eases the ability for Python uses to add intercept hooks to
change how the basic Ledger module functions. An example of what should
be possible soon:
import ledger
def my_foo_handler(value):
print "--foo received:", value
ledger.add_handler(ledger.Option, "foo=", my_foo_handler)
|