summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* 'make check' for gcov shouldn't listen to -jJohn Wiegley2010-06-233-4/+6
|
* Added a command-line test runner named test/runJohn Wiegley2010-06-221-0/+45
|
* Added report query modifiers: for, since, untilJohn Wiegley2010-06-225-47/+131
| | | | | | | | | Now instead of ledger reg expense -p "this month", you can say: ledger reg expense for this month And as a shorthand for "for until this month", you can just say "until this month" or "since this month".
* Extended feat-fixated-prices.testJohn Wiegley2010-06-221-0/+12
|
* Price annotation no longer inject an implied costJohn Wiegley2010-06-227-3176/+2979
| | | | | | | | | | | | | | | | | | | | | | | Consider the following transaction: 2010-06-22 Sample Assets:Brokerage 10 AAPL {$30} Assets:Brokerage Previously, this would have been equivalent to: 2010-06-22 Sample Assets:Brokerage 10 AAPL @ $30 Assets:Brokerage However, this is not always what the user expects to happen. When @ is not being used, the transaction should reflect a mere transfer of commodities. This is now how it works, and thus the above transaction is now equivalent to the following instead: 2010-06-22 Sample Assets:Brokerage 10 AAPL {$30} Assets:Brokerage -10 AAPL {$30}
* Don't do cost finalization for auto/period xactsJohn Wiegley2010-06-221-48/+50
|
* Added has_date() method to item_tJohn Wiegley2010-06-221-0/+4
|
* The notions of "now" and "today" now use local timeJohn Wiegley2010-06-221-3/+3
|
* Added new "bold" modifier to query expressionsJohn Wiegley2010-06-227-133/+175
| | | | | | | | | | | | | | For example: ledger bal assets bold checking Or you can use expressions: ledger bal assets bold '=total > 1000' This last is identical to saying: ledger bal -l 'account =~ /assets/' --bold-if='total > 1000'
* Regression and generate tests now fail properlyJohn Wiegley2010-06-222-12/+18
|
* Added new --bold-if optionJohn Wiegley2010-06-224-17/+61
|
* Balances and sequences can be compared to amountsJohn Wiegley2010-06-221-16/+4
|
* Fixed typo in previous commit's regression testJohn Wiegley2010-06-211-1/+1
|
* bal was sometimes reporting empty accountsJohn Wiegley2010-06-214-6/+31
|
* Change weighting of account-name abbreviationJohn Wiegley2010-06-216-9/+9
| | | | | Parent accounts are abbreviated even more, so that child accounts can show more text.
* Added a regression test for the previous commitJohn Wiegley2010-06-211-0/+12
|
* Corrected a major flaw in the transaction finalizerJohn Wiegley2010-06-211-2/+3
| | | | | | When a transaction has two commodities, but also a null posting, no attempt should be made to resolve the costs in terms of the primary commodity.
* Improvements to time period parsingJohn Wiegley2010-06-211-8/+190
| | | | | Things like "since last month" and "4 weeks ago", and "since 4 weeks ago" are now all working.
* Added tests for sole budget/forecast reportsJohn Wiegley2010-06-212-0/+86
|
* Corrected a compilation warningJohn Wiegley2010-06-211-2/+3
|
* Fixed an incorrect path in tools/proofJohn Wiegley2010-06-211-2/+2
|
* Transactions no longer needed for budget/forecastJohn Wiegley2010-06-201-4/+6
| | | | | This means you can forecast or budget against a file containing only periodic transactions.
* Output budget even if no postings directly matchedJohn Wiegley2010-06-202-4/+2
|
* Don't warn about --import in doc when --no-pythonJohn Wiegley2010-06-201-1/+8
|
* Added missing call to resolve_end() in find_periodJohn Wiegley2010-06-202-0/+74
|
* Factored out some unused local variablesJohn Wiegley2010-06-201-9/+5
|
* Rename dow_posts to day_of_week_posts, to be clearerJohn Wiegley2010-06-203-10/+10
|
* If fixated price commodities are mixed, show themJohn Wiegley2010-06-204-23/+95
| | | | | | | | | | | For example, if a Ledger file contains transactions with the use of both EUR and EUR {=PRICE}, then regular reports will always show the {=PRICE}, disabling the by-name commodity merging that takes place. In brief, fixated and non-fixated commodities are now non-mergable. If a file contains all of one, or all of the other, they will still be merged, since these separate usages do not conflict the way that fixated and non-fixated together do.
* If a posting's price has an annotation tag, save itJohn Wiegley2010-06-201-25/+33
|
* --input-date-format now affects dates with timesJohn Wiegley2010-06-201-1/+8
|
* Do not record market values for fixated exchangesJohn Wiegley2010-06-201-1/+7
| | | | | | Do not record commodity exchanges where amount's commodity has a fixated price, since this does not establish a market value for the base commodity.
* Only run the CheckTests if DEBUG mode is enabledJohn Wiegley2010-06-201-1/+5
|
* When anonymizing posts, remove the transaction codeJohn Wiegley2010-06-201-0/+1
|
* Added debug print for commodity.prices.findJohn Wiegley2010-06-201-0/+2
|
* Regression test for last commitJohn Wiegley2010-06-201-0/+24
|
* If a periodic posting terminates, stop forecasting with itJohn Wiegley2010-06-201-4/+5
|
* Subsantial fixes and improvements to budgetingJohn Wiegley2010-06-197-16/+164
| | | | | | | | | 1. A bounded budget "from DATE to DATE" will now generate entries throughout that entire range, if it is triggered. 2. An unbounded budget begins, as before, in the timeframe of the reported posting which triggered it, but now continues until the present date.
* Fix to the way simplified regressions tests are readJohn Wiegley2010-06-191-1/+1
|
* Initial skeleton for the 3.0 manualJohn Wiegley2010-06-191-0/+322
|
* Corrected a bug in report query parsingJohn Wiegley2010-06-192-6/+6
|
* query command's parsing behavior sensitive to -nJohn Wiegley2010-06-191-1/+2
| | | | | | | | | | With -n, the first argument is parsed as a string containing subarguments. Otherwise, each argument is parsed as a separate argument. In short, the -n mode mimicks what happens when the query expr after "=" is parsed for automated expressions. The non -n mode mimicks what happens at the command line for users.
* Made amount_t::value a bit saferJohn Wiegley2010-06-191-5/+6
|
* Added NEWS entries for 2.6.2 and 2.6.3John Wiegley2010-06-191-0/+17
|
* When --inject is used for a tag, convert to an amountJohn Wiegley2010-06-181-14/+8
|
* Renamed the "Rounding" account to "Adjustment"John Wiegley2010-06-181-1/+1
|
* Filename globs now surrounded by ^$John Wiegley2010-06-181-2/+2
|
* Fixed bug that had broken any() and all()John Wiegley2010-06-181-1/+1
|
* Fixed register formatting of postings with payeesJohn Wiegley2010-06-181-1/+2
|
* Made "convert" command insensitive to null amountsJohn Wiegley2010-06-181-12/+14
|
* Added new option --inject=KEY[,KEY...]John Wiegley2010-06-187-1/+89
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If you have a typed metadata key which contains an amount, you can use --inject=KEY to inject a posting with that amount wherever a match occurs. There are two main forms of usage: 2010-06-18 Sample ; Key:: $100 Expenses:Food $100.00 Assets:Checking The command would be: ledger reg --inject=Key In the above, transactional form, a posting under the account "Key" will be injected before the first posting reported for this transaction. It's amount will be $100. This only happens once for the whole transaction. It is also possible to associate the key with a posting: 2010-06-18 Sample Expenses:Food $100.00 ; Key:: $100 Assets:Checking Now the injected posting is generated whenever that particular post is reported.