| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
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.
|
| |
|
|
| |
The journal_t now completely represents the data part of a session.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
It is now a full parser that parses report queries directly into value
expression trees. These then get rendered into text so that other
options may extend the expression.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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 was causing budget totals not to appear in balance reports.
Fixes 8254755E-7B61-47C8-B48E-A2A7FD79EB80
|
| |
|
|
| |
t = display_amount, T = display_total
|
| |
|
|
|
|
|
| |
Note that sorting on the "total" is not the same thing as sorting on the
"display_total" when multiple commodities are in use and the -X flag is
selected! One should always sort on display_total, since that's the
value which is shown in the report. 'T' is a synonym for display_total.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
For example, if you had 100 AU (onces of gold) and wanted to report it
in dollars, but at a price of $997 per ounce, you could now easily say:
ledger bal -X '$,AU=$997'
|
| |
|
|
|
|
|
| |
This means that final balance valuations (with -V or -X) will be done in
terms of the date given to --end, rather than based on the current day.
Fixes 647D5DB9-DBBB-47C8-80CE-F3F70E3B0253
|
| |
|
|
|
|
|
|
| |
This is necessary in order to redden negative amounts correctly under
all circumstances, such as component amounts of a multi-commodity
balance.
Fixes 727B2DF8-A2A1-4716-9C15-547F20D5F933
|
| |
|
|
|
| |
This reports which options are in place before invoking a command, and
where exactly each option value came from.
|
| | |
|
| |
|
|
|
|
|
| |
It is no longer done in calc_posts, but recursively on each account.
This allows value expressions to ask statistical questions, like
"earliest cleared posting?" (TBD) from any specific account, computed
lazily.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Although %(amount) inserts an item's amount, it only does exactly that.
There is no special consideration like stripping of lot details, or
reduction to the base commodity, etc. For those things, and to make
sure it was display in red if negative, the canonical form would be:
%(ansify_if(justify(scrub(amount), 12, -1, true), red if amount < 0))
You can now use the special %{} form as an alternate to this:
%12{amount, red if amount < 0}
The two expand to the same underlying expression.
|
| | |
|
| | |
|
| | |
|
