Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Added "source" command, for executing valexpr files | John Wiegley | 2010-06-24 | 3 | -0/+30 |
| | |||||
* | Fixed how valexpr function defs and calls work | John Wiegley | 2010-06-24 | 1 | -15/+32 |
| | |||||
* | Scopes can now provide a description of themselves | John Wiegley | 2010-06-24 | 8 | -0/+88 |
| | | | | | | This isn't being used yet, but it likely will to improve the information presented to users if their value expressions fail to compile or evaluate. | ||||
* | Value scopes now take a parent scope for chaining | John Wiegley | 2010-06-24 | 2 | -16/+9 |
| | |||||
* | "only" now a report query modifier for --only | John Wiegley | 2010-06-24 | 3 | -20/+31 |
| | | | | This fits with "show" and "bold", etc. | ||||
* | Merge branch 'next' | John Wiegley | 2010-06-23 | 91 | -3638/+4999 |
|\ | |||||
| * | v3.0.0-20100623 (b2) | John Wiegley | 2010-06-23 | 1 | -1/+1 |
| | | |||||
| * | Remove use of --enable-cache in tools/push | John Wiegley | 2010-06-23 | 1 | -1/+1 |
| | | |||||
| * | 'make check' for gcov shouldn't listen to -j | John Wiegley | 2010-06-23 | 3 | -4/+6 |
| | | |||||
| * | Added a command-line test runner named test/run | John Wiegley | 2010-06-22 | 1 | -0/+45 |
| | | |||||
| * | Added report query modifiers: for, since, until | John Wiegley | 2010-06-22 | 5 | -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.test | John Wiegley | 2010-06-22 | 1 | -0/+12 |
| | | |||||
| * | Price annotation no longer inject an implied cost | John Wiegley | 2010-06-22 | 7 | -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 xacts | John Wiegley | 2010-06-22 | 1 | -48/+50 |
| | | |||||
| * | Added has_date() method to item_t | John Wiegley | 2010-06-22 | 1 | -0/+4 |
| | | |||||
| * | The notions of "now" and "today" now use local time | John Wiegley | 2010-06-22 | 1 | -3/+3 |
| | | |||||
| * | Added new "bold" modifier to query expressions | John Wiegley | 2010-06-22 | 7 | -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 properly | John Wiegley | 2010-06-22 | 2 | -12/+18 |
| | | |||||
| * | Added new --bold-if option | John Wiegley | 2010-06-22 | 4 | -17/+61 |
| | | |||||
| * | Balances and sequences can be compared to amounts | John Wiegley | 2010-06-22 | 1 | -16/+4 |
| | | |||||
| * | Fixed typo in previous commit's regression test | John Wiegley | 2010-06-21 | 1 | -1/+1 |
| | | |||||
| * | bal was sometimes reporting empty accounts | John Wiegley | 2010-06-21 | 4 | -6/+31 |
| | | |||||
| * | Change weighting of account-name abbreviation | John Wiegley | 2010-06-21 | 6 | -9/+9 |
| | | | | | | | | | | Parent accounts are abbreviated even more, so that child accounts can show more text. | ||||
| * | Added a regression test for the previous commit | John Wiegley | 2010-06-21 | 1 | -0/+12 |
| | | |||||
| * | Corrected a major flaw in the transaction finalizer | John Wiegley | 2010-06-21 | 1 | -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 parsing | John Wiegley | 2010-06-21 | 1 | -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 reports | John Wiegley | 2010-06-21 | 2 | -0/+86 |
| | | |||||
| * | Corrected a compilation warning | John Wiegley | 2010-06-21 | 1 | -2/+3 |
| | | |||||
| * | Fixed an incorrect path in tools/proof | John Wiegley | 2010-06-21 | 1 | -2/+2 |
| | | |||||
| * | Transactions no longer needed for budget/forecast | John Wiegley | 2010-06-20 | 1 | -4/+6 |
| | | | | | | | | | | This means you can forecast or budget against a file containing only periodic transactions. | ||||
| * | Output budget even if no postings directly matched | John Wiegley | 2010-06-20 | 2 | -4/+2 |
| | | |||||
| * | Don't warn about --import in doc when --no-python | John Wiegley | 2010-06-20 | 1 | -1/+8 |
| | | |||||
| * | Added missing call to resolve_end() in find_period | John Wiegley | 2010-06-20 | 2 | -0/+74 |
| | | |||||
| * | Factored out some unused local variables | John Wiegley | 2010-06-20 | 1 | -9/+5 |
| | | |||||
| * | Rename dow_posts to day_of_week_posts, to be clearer | John Wiegley | 2010-06-20 | 3 | -10/+10 |
| | | |||||
| * | If fixated price commodities are mixed, show them | John Wiegley | 2010-06-20 | 4 | -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 it | John Wiegley | 2010-06-20 | 1 | -25/+33 |
| | | |||||
| * | --input-date-format now affects dates with times | John Wiegley | 2010-06-20 | 1 | -1/+8 |
| | | |||||
| * | Do not record market values for fixated exchanges | John Wiegley | 2010-06-20 | 1 | -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 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 |
| | |