| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* 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
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
There was a if statement with an inverse boolean meaning, which caused
some automated transaction postings to have a null amount.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The last commit did not contain the majority of changes because of a
slight mishap. This contains the real changeset.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
To better follow naming standards used in the accounting community --
particularly those relating to double-entry accounting -- the following
technical terms in Ledger have been changed:
- what was "entry" is now "transaction"
- what was "transaction" is now "posting"
Correspondingly, the shorthand names "entry" and "xact" have been
changed to "xact" and "post", respectively.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
It turns out this is needed in order to properly close the pager
subprocess.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This option sets the total by which revalued transactions are
determined. Only needed if the display total is not appropriate.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
These are for dealing with sequences.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In the old scheme, nested values would simply flatten and concatenate,
so that '((1, 2), 3) = (1, 2, 3)'. Now sublists are preserved, so that
sequences may be passed as arguments to functions.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
It is true if every member of the sequence passes the test.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|