| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
| |
For example, just the word "account" returns the name of the current
posting's account, but account("Expenses:Food") returns the actual
account object, so that it's total may be accessed.
|
| |
|
|
|
|
| |
Fixes #211 / 1736ACA5-5DE6-4826-AEB4-DB5B2A2217AC
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
|
|
|
|
|
| |
Ledger can often figure this out for itself, but this flag just makes it
the default behavior. It is meant to be added to one's ~/.ledgerrc
file.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The journal_t now completely represents the data part of a session.
|
|
|
|
|
| |
This allows journal_t objects to be completed serialized to disk and
deserialized.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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 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 reports which options are in place before invoking a command, and
where exactly each option value came from.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These strings are now collected automagically in the file po/ledger.pot.
If you'd like to produce a translation, just run this command after
building Ledger:
msginit -l LOCALE -o LANG.po -i po/ledger.pot
Where LOCALE is a string like de or en_GB, and LANG is a short
descriptive word for your language.
Then send me this .po file so I can commit it to the Ledger sources
(alternatively, you could maintain the file in a fork on GitHub), and
setup the build script to format and install your new message catalog
during a "make install".
|
| |
|
| |
|
|
|
|
|
| |
The last commit did not contain the majority of changes because of a
slight mishap. This contains the real changeset.
|
|
|
|
|
|
|
| |
This is like -V, except it lets you specify the goal commodity to report
in terms of, for example:
reg -x CAD
|
| |
|
|
|
|
|
|
|
| |
When enabled, if any accounts or commodities are seen in an uncleared
transaction, which were not seen previously in a cleared or pending
transaction or a textual directive dealing with accounts or commodities,
a warning is generated about the unknown item.
|
| |
|
|
|
|
|
| |
You now call session_t::close_journal_files() followed by
session_t::read_journal_files().
|
|
|
|
|
|
|
| |
Created a new function, session_t::reread_journal_files, which throws
away all previous state data and reads in the same files again. This is
needed to allow Emacs to communicate with Ledger via the REPL, so that
it tell Ledger when it has made changes to the user's data file.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Example:
] expr f(x) := x + 100
] expr f(100)
200
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
For example, "ledger eval options.limit" prints 0 (for false), but:
"ledger -l hello eval options.limit" print "hello"s, since the value of
options.limit, once set to a value, is that string. For flag options,
such as -Y, eval prints 0 if unset, and 1 if set.
This feature allows value expressions to be conditionalized based on the
presence of user options.
|
| |
|
| |
|