summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* Allow integers to be multiplied with amountsJohn Wiegley2009-06-151-0/+1
| | | | Fixes other part of 04C5E1CA-1B39-4214-81C7-FD5AA785308F
* Ignore attempts to annotate the null commodityJohn Wiegley2009-06-151-1/+1
| | | | Fixes 04C5E1CA-1B39-4214-81C7-FD5AA785308F
* If a posting comment is very short, let it hangJohn Wiegley2009-06-141-3/+5
| | | | This applies when using the "print" report, or the "comment" variable.
* Strip annotations before handling bal assignmentsJohn Wiegley2009-06-131-1/+2
|
* Added new debug option --optionsJohn Wiegley2009-06-0210-167/+392
| | | | | This reports which options are in place before invoking a command, and where exactly each option value came from.
* Added % suffix operator, as in "$1.00 * 10%"John Wiegley2009-05-264-4/+22
|
* Fix pointer const-ness in parse_tags()Andrew Potter2009-05-261-2/+2
|
* Corrected a syntax error in a gettext usageJohn Wiegley2009-03-241-1/+1
|
* Don't instantiate duration_t using default ctorJohn Wiegley2009-03-231-10/+11
|
* Rewrote the date interval parser/stepperJohn Wiegley2009-03-234-24/+102
| | | | | The new implementation uses boost::gregorian::date_duration objects, rather than manually stepping.
* The new code is working now.John Wiegley2009-03-166-63/+68
|
* Restored all the old code, though not tested yetJohn Wiegley2009-03-161-22/+22
|
* Added feature to "align" the interval's start dateJohn Wiegley2009-03-152-38/+145
|
* First iteration of the new date_interval_t rewriteJohn Wiegley2009-03-158-273/+389
|
* Added a missing * operationJohn Wiegley2009-03-151-1/+1
|
* Removed an unnecessary member variableJohn Wiegley2009-03-151-1/+0
|
* Started breaking up interval_t into range_tJohn Wiegley2009-03-151-14/+43
|
* If 2+ child accounts are shown, show the parentJohn Wiegley2009-03-152-14/+19
| | | | | Also, also show a final balance if there are multiple accounts displayed, even if that final balance is zero.
* If a balance report is multi-lined, print a totalJohn Wiegley2009-03-151-10/+1
|
* Moved a variable initializationJohn Wiegley2009-03-111-2/+2
|
* Enabled use of pre-compiled headers by defaultJohn Wiegley2009-03-1063-2/+124
|
* Normalized some #ifdef's to #if definedJohn Wiegley2009-03-101-3/+3
|
* Disabled warning on not finding ledger/__init__.pyJohn Wiegley2009-03-091-1/+4
| | | | | This warning is completely harmless, and was downgraded to a debug message.
* Rewrote acprep in Python and improved the buildJohn Wiegley2009-03-091-16/+2
|
* Added support for "today" as a time periodJohn Wiegley2009-03-081-1/+11
|
* Rewrote the balance report again, to fix --depthJohn Wiegley2009-03-085-56/+53
|
* Fixed a few minor cases of uninitialized variablesJohn Wiegley2009-03-084-6/+7
|
* Fixed a reference to uninitialized memoryJohn Wiegley2009-03-071-1/+1
| | | | | This was only found with _GLIBCXX_DEBUG=1 *and* coverage analysis (-fprofile-arcs -ftest-coverage).
* Revised the ways statistics are computedJohn Wiegley2009-03-067-189/+237
| | | | | | | It is no longer done in calc_posts, but recursively on each account. This allows value expressions to ask statistical questions, like "earliest cleared posting?" (TBD) from any specific account, computed lazily.
* Changed the way that account balances are computedJohn Wiegley2009-03-068-83/+234
|
* Implemented --unround using value expressionsJohn Wiegley2009-03-064-29/+14
|
* Don't compute running total for balance reportsJohn Wiegley2009-03-053-19/+23
|
* Removed the --totals optionJohn Wiegley2009-03-054-10/+2
|
* Enriched the behavior of post_t::add_to_valueJohn Wiegley2009-03-051-3/+21
| | | | | The new behavior will be used in future by some pending topic branches I'm working on.
* Renamed some flags and members in post_tJohn Wiegley2009-03-054-30/+33
|
* Added a value_t macro: VALUE_OR_VEROJohn Wiegley2009-03-051-0/+2
|
* If Python is not in use, global includes sessionJohn Wiegley2009-03-051-0/+2
|
* Reduced the #include dependency tree to a minimumJohn Wiegley2009-03-0480-153/+204
|
* Cured several harmless compiler warningsJohn Wiegley2009-03-046-4/+12
|
* Changed many assert() calls to VERIFY()John Wiegley2009-03-048-54/+49
|
* Corrected a build error if Python support missingJohn Wiegley2009-03-031-0/+4
|
* Gather account details in a details_t structureJohn Wiegley2009-03-037-35/+49
|
* Normalized how account totals are calculatedJohn Wiegley2009-03-039-129/+68
|
* Added a new "account_amount" valexpr functionJohn Wiegley2009-03-031-0/+31
| | | | At the moment, it's only useful during parsing.
* If a posting has an integer amount, convert itJohn Wiegley2009-03-031-3/+7
|
* Added ; as a sequencing operator in valexprsJohn Wiegley2009-03-035-2/+58
|
* Fixed parsing of '(1, 2, (3, 4))'John Wiegley2009-03-033-1/+12
|
* Allow special %{} formatting sequenceJohn Wiegley2009-03-033-32/+122
| | | | | | | | | | | | | | | Although %(amount) inserts an item's amount, it only does exactly that. There is no special consideration like stripping of lot details, or reduction to the base commodity, etc. For those things, and to make sure it was display in red if negative, the canonical form would be: %(ansify_if(justify(scrub(amount), 12, -1, true), red if amount < 0)) You can now use the special %{} form as an alternate to this: %12{amount, red if amount < 0} The two expand to the same underlying expression.
* Made all the ANSI color names into valexpr namesJohn Wiegley2009-03-031-0/+67
|
* Made error reporting while parsing more resilientJohn Wiegley2009-03-032-7/+7
|