| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 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)
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This sets how many years of forecasting Ledger will do before it
terminates the attempt.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Because --daily is more commonly desired, and fits the pattern of the
other periodic switches:
-D --daily
-W --weekly
-M --monthly
-Y --yearly
Only --quarterly doesn't have its own short option.
|
| |
|
|
|
|
|
| |
This is so that if someone has --effective in their .ledgerrc, they can
force the use of actual dates.
|
|
|
|
|
|
| |
This sets Ledger's notion of the "current time" to the given date. This
makes it possible to have stable output from budgeting and forecasting
reports, for the sake of baseline tests.
|
| |
|
| |
|
|
|
|
|
|
| |
This is a balance report with three columns:
Current balance | Cleared balance | Last cleared date
|
|
|
|
|
|
| |
This is a balance report with four columns:
Amount spent | Budgeted Amount | Difference | Percentage
|
| |
|
| |
|
|
|
|
|
|
|
| |
This option reports only in terms of the annotated price of the
commodities involved, otherwise it reports the amounts themselves. It
can be used in conjunction with other reports, as it applies to the
displayed amounts, not the actual amounts being calculated.
|
| |
|
|
|
|
|
|
| |
commodity.h - code for commodity_t
annotate.h - commodity annotations
pool.h - commodity pool management
|
|
|
|
|
|
| |
The problem at this point is that it's recording prices in the price
database multiple times; it should only need to download a price for
each commodity once per day.
|
| |
|
|
|
|
| |
This option is just an alias for --sort-xacts.
|