| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This way, if the running total is off by a penny or two due to rounding
of one or more commodities in the account, the user will see it.
This commit also reorganizes the testing code a bit, which I did after
adding the ninth test series (ConfirmTests), to validate the new
rounding code.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When an amount is truncated, it drops all of the extra precision and
becomes exactly the value would have seen were it printed.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The result is that every member of the sequence has the given operation
applied.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Thus, you can say "$100 + 10" to increase it by $10.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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".
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
A final null account (no amount specified) is now taken to be the "from"
account, not another "to" account.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* lisp/ledger.el: Use vector notation for the backspace key.
Say "[backspace]" rather than "(kbd "<backspace>")".
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* lisp/ledger.el: When starting ledger-report, print a help message.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* lisp/ledger.el: Make backspace scroll down in ledger-report buffers.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* lisp/ledger.el: Make ledger-report buffers non-editable.
Intuitively, a ledger-report buffer is a report -- the result of
applying a function to your ledger data. Thus, the buffers created by
ledger-reports aren't editable text; to "change" the ledger-report
buffer, change the ledger data from which the report is derived.
This commit alters ledger-report and ledger-report-redo.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* lisp/ledger.el: Indicate what the report name is in report buffers
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is because soon, I intend to have real Python source files in
python/.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
If a commodity has never been seen before, and it is used in a cost
amount, remember the display flags.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Whenever a commodity is exchanged for another in a posting, one of the
two is considered "primary", and the other secondary. Primariness of a
commodity is remembered, since the --market option only renders balances
into secondary commodities, never primaries. To render primaries, use
the --exchange=COMMODITY option.
In all of the following examples, the P commodity is considered primary
and the S is secondary (the P at the beginning of the line indicates a
price-setting directive):
2009/01/01 Sample 1a
Assets:Brokerage:Stocks 100 S
Assets:Brokerage:Cash -100 P
P 2009/01/15 00:00:00 S 2 P
2009/02/01 Sample 2a
Assets:Brokerage:Stocks 100 S @ 1 P
Assets:Brokerage:Cash
P 2009/02/01 00:00:00 S 4 P
2009/03/01 Sample 3a
Assets:Brokerage:Stocks 100 S @@ 100 P
Assets:Brokerage:Cash
P 2009/03/01 00:00:00 S 8 P
2009/04/01 Sample 4a
Assets:Brokerage:Cash 100 P
Assets:Brokerage:Stocks -100 S {1 P}
P 2009/04/01 00:00:00 S 16 P
|
| | | | | | |
|
| | | | | | |
|