Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Only run the CheckTests if DEBUG mode is enabled | John Wiegley | 2010-06-20 | 1 | -1/+5 |
| | |||||
* | When anonymizing posts, remove the transaction code | John Wiegley | 2010-06-20 | 1 | -0/+1 |
| | |||||
* | Added debug print for commodity.prices.find | John Wiegley | 2010-06-20 | 1 | -0/+2 |
| | |||||
* | Regression test for last commit | John Wiegley | 2010-06-20 | 1 | -0/+24 |
| | |||||
* | If a periodic posting terminates, stop forecasting with it | John Wiegley | 2010-06-20 | 1 | -4/+5 |
| | |||||
* | Subsantial fixes and improvements to budgeting | John Wiegley | 2010-06-19 | 7 | -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 read | John Wiegley | 2010-06-19 | 1 | -1/+1 |
| | |||||
* | Initial skeleton for the 3.0 manual | John Wiegley | 2010-06-19 | 1 | -0/+322 |
| | |||||
* | Corrected a bug in report query parsing | John Wiegley | 2010-06-19 | 2 | -6/+6 |
| | |||||
* | query command's parsing behavior sensitive to -n | John Wiegley | 2010-06-19 | 1 | -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 safer | John Wiegley | 2010-06-19 | 1 | -5/+6 |
| | |||||
* | Added NEWS entries for 2.6.2 and 2.6.3 | John Wiegley | 2010-06-19 | 1 | -0/+17 |
| | |||||
* | When --inject is used for a tag, convert to an amount | John Wiegley | 2010-06-18 | 1 | -14/+8 |
| | |||||
* | Renamed the "Rounding" account to "Adjustment" | John Wiegley | 2010-06-18 | 1 | -1/+1 |
| | |||||
* | Filename globs now surrounded by ^$ | John Wiegley | 2010-06-18 | 1 | -2/+2 |
| | |||||
* | Fixed bug that had broken any() and all() | John Wiegley | 2010-06-18 | 1 | -1/+1 |
| | |||||
* | Fixed register formatting of postings with payees | John Wiegley | 2010-06-18 | 1 | -1/+2 |
| | |||||
* | Made "convert" command insensitive to null amounts | John Wiegley | 2010-06-18 | 1 | -12/+14 |
| | |||||
* | Added new option --inject=KEY[,KEY...] | John Wiegley | 2010-06-18 | 7 | -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. | ||||
* | A metadata key must occur at the beginning | John Wiegley | 2010-06-18 | 1 | -1/+3 |
| | | | | | | | | | Before, this was valid: ; Today Yesterday: Tomorrow Which would set the key Yesterday to the value Tomorrow. Now, it is just an ordinary comment. | ||||
* | Minor fix to the way transfer_details sets post date | John Wiegley | 2010-06-18 | 1 | -1/+1 |
| | |||||
* | has_tag and get_tag now take an 'inherit' parameter | John Wiegley | 2010-06-18 | 4 | -26/+37 |
| | |||||
* | Corrected printing of assigned amounts | John Wiegley | 2010-06-18 | 1 | -1/+1 |
| | |||||
* | Only look for [date] outside of metadata entries | John Wiegley | 2010-06-18 | 1 | -16/+16 |
| | |||||
* | Individual postings may each have their own payee | John Wiegley | 2010-06-17 | 6 | -8/+19 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If a posting has the metadata field "Payee" set to a string, that will be used as the payee name for that posting. This affects the register report, the payees report, and the --by-payee option. This is useful because sometimes I send, say, 4 checks at a time to my bank. So on my bank statement, this is all just one amount: 2010-06-17 Sample Assets:Bank $400.00 Income:Check1 $-100.00 Income:Check2 $-100.00 Income:Check3 $-100.00 Income:Check4 $-100.00 Though it's important that the Assets:Bank posting be a single posting of $400 value, I'd like for income reports to show whom each check came from. Now I can say: 2010-06-17 Sample Assets:Bank $400.00 Income:Check1 $-100.00 ; Payee: Person One Income:Check2 $-100.00 ; Payee: Person Two Income:Check3 $-100.00 ; Payee: Person Three Income:Check4 $-100.00 ; Payee: Person Four When I report this, it appears as: 10-Jun-17 Sample Assets:Bank $400.00 $400.00 Person One Income:Check1 $-100.00 $300.00 Person Two Income:Check2 $-100.00 $200.00 Person Three Income:Check3 $-100.00 $100.00 Person Four Income:Check4 $-100.00 0 This shows that they are all in the same transaction (which is why the date is not repeated), but they have different payees. | ||||
* | Improvements to tools/speed-test.sh | John Wiegley | 2010-06-17 | 1 | -6/+4 |
| | |||||
* | Created a script to check commenting coverage | John Wiegley | 2010-06-15 | 1 | -0/+121 |
| | |||||
* | Ensure that all options are tested and documented | John Wiegley | 2010-06-15 | 21 | -1/+88 |
| | |||||
* | Don't build gcov Ledger with asserts enabled | John Wiegley | 2010-06-15 | 1 | -3/+10 |
| | |||||
* | Updated MacPorts Portfile | John Wiegley | 2010-06-15 | 1 | -30/+15 |
| | |||||
* | Extended proof/push to upload tarballs/gcov | John Wiegley | 2010-06-15 | 2 | -8/+32 |
| | |||||
* | v3.0.0-20100615 | John Wiegley | 2010-06-15 | 1 | -1/+1 |
| | |||||
* | Corrected the 'report' rule in Makefile.am | John Wiegley | 2010-06-15 | 1 | -3/+3 |
| | |||||
* | Merge branch 'next' | John Wiegley | 2010-06-15 | 33 | -139/+242 |
|\ | |||||
| * | Changes for building with Visual Studio 2008 | John Wiegley | 2010-06-15 | 18 | -28/+42 |
| | | |||||
| * | Corrected list of options shown in the man page | John Wiegley | 2010-06-15 | 1 | -8/+39 |
| | | |||||
| * | Removed unused --unsorted option | John Wiegley | 2010-06-15 | 6 | -13/+3 |
| | | |||||
| * | Version information is now based on version.m4 | John Wiegley | 2010-06-15 | 5 | -63/+49 |
| | | |||||
| * | Tests run in parallel with using acprep -jX make | John Wiegley | 2010-06-15 | 5 | -27/+109 |
|/ | | | | | This is done using the multiprocessing library in Python 2.6. If that's unavailable, this feature does nothing. | ||||
* | Merge branch 'next' | John Wiegley | 2010-06-14 | 64 | -511/+785 |
|\ | |||||
| * | Support period expressions "this/next/last week" | John Wiegley | 2010-06-14 | 1 | -14/+28 |
| | | |||||
| * | Allow period exprs "from today", "until tomorrow" | John Wiegley | 2010-06-14 | 1 | -0/+10 |
| | | |||||
| * | Support period expressions like "last 4 weeks" | John Wiegley | 2010-06-14 | 1 | -12/+37 |
| | | |||||
| * | Fix to allow time periods like "every 14 days" | John Wiegley | 2010-06-14 | 1 | -1/+1 |
| | | |||||
| * | Improved algorithm for abbreviating account names | John Wiegley | 2010-06-14 | 34 | -231/+354 |
| | | |||||
| * | Made >>>2 and === optional in regression tests | John Wiegley | 2010-06-14 | 1 | -5/+6 |
| | | |||||
| * | Added `ledger-update-test' to ldg-texi.el | John Wiegley | 2010-06-14 | 1 | -0/+20 |
| | | |||||
| * | Added initial implementation of lot_*() functions | John Wiegley | 2010-06-14 | 2 | -1/+37 |
| | | |||||
| * | Don't elide quotes for all-digit commodities | John Wiegley | 2010-06-14 | 1 | -3/+7 |
| | | |||||
| * | Revised how Ledger handles the "current year" | John Wiegley | 2010-06-14 | 16 | -152/+126 |
| | | | | | | | | | | Now when the Y directive sets the current year for a region, it affects everything, as if the clock really were set back to that year. |