summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* Guard against using an uninitialized valueJohn Wiegley2010-01-181-1/+4
| | | | Fixes DDB54BB8-8C1C-4129-A137-07A38068F3BE
* Fix for date parsing when no year is givenJohn Wiegley2010-01-161-1/+1
|
* Cost of a post with neg. amount should be negativeJohn Wiegley2009-12-073-2/+8
|
* Allow relative includes in the current directoryJohn Wiegley2009-12-071-4/+10
|
* Added some debugging code related to boost::regexJohn Wiegley2009-11-251-0/+2
|
* Added support for a "fixed" directiveJohn Wiegley2009-11-254-21/+75
| | | | | | | | | | | | | | | | | | | It lets you specify a fixed cost for a duration of a ledger file, for example: fixed ecu $2 2008/01/01 income assets:bank:checking 1 ecu income:salary end fixed This is equivalent to: 2008/01/01 income assets:bank:checking 1 ecu {=$2} income:salary
* Added a trim() value expression functionJohn Wiegley2009-11-252-0/+29
|
* * and | now comment chars, for the sake of Org-modeJohn Wiegley2009-11-251-2/+4
|
* Added options: --unrealized-gains and --unrealized-lossesAristid Breitkreuz2009-11-243-2/+19
| | | | | | | | | | | These options allow the user to specify what accounts names should be used for these two types of accounts. They are optional, and default to: --unrealized-gains "Equity:Unrealized Gains" --unrealized-losses "Equity:Unrealized Losses" These are intended to be set in one's ~/.ledgerrc file.
* Very minor but easy optimization for symbol_scope_tJohn Wiegley2009-11-242-11/+15
| | | | | | | Lots of symbol_scope_t throwaway objects get created during value expression calculation, and 99% of them are never used. Therefore, the std::map which each contains is now within an optional<> wrapper, so that no constructor happens unless one is actually used.
* Don't migrate commodity details from pricing entriesJohn Wiegley2009-11-241-1/+1
|
* Whitespace fixJohn Wiegley2009-11-241-2/+4
|
* Added even more missing virtual keywords!John Wiegley2009-11-222-2/+2
|
* Added several more missing virtual keywordsJohn Wiegley2009-11-216-6/+6
|
* Added a missing virtual keywordJohn Wiegley2009-11-211-2/+1
|
* The Python web server now uses jQuery TablesorterJohn Wiegley2009-11-212-7/+14
|
* Fixed Ledger/Python byte vs. char Unicode bridgeJohn Wiegley2009-11-207-22/+54
|
* Added string conversion op for amounts and balancesJohn Wiegley2009-11-202-0/+12
|
* Don't rely on the integral value of a booleanJohn Wiegley2009-11-201-2/+5
|
* Normalized the value() method for Python numericsJohn Wiegley2009-11-203-27/+37
|
* Added more documentation to python/demo.pyJohn Wiegley2009-11-201-4/+10
|
* Many improvements to Ledger's Python bindingsJohn Wiegley2009-11-1924-201/+321
|
* Added an --unrealized option, for use with bal -VJohn Wiegley2009-11-195-15/+74
| | | | | | When this option is on, then in balance report which show market values, any gains or losses in value will be balanced into a pair of accounts called Equity:Unrealized Gains and Equity:Unrealized Losses.
* Fixed a debug stringJohn Wiegley2009-11-191-2/+1
|
* Don't auto-sort transactions for the balance reportJohn Wiegley2009-11-191-4/+0
|
* Changed several pointers to references in filtersJohn Wiegley2009-11-193-50/+48
|
* Renamed bool controlling running total calculationsJohn Wiegley2009-11-183-6/+6
| | | | | | It used to be "account_wise", since it only happens for non-account-wise reports. Now it's called just "calc_running_total", so anyone can request it.
* Decompile all amount expressions for accounts reportsJohn Wiegley2009-11-181-0/+6
| | | | | This happens after running through all the post handlers, before running any of the account handlers.
* It's OK for a report query to be emptyJohn Wiegley2009-11-182-28/+20
| | | | It's always possible the user only specified a display predicate.
* Whitespace fixJohn Wiegley2009-11-181-2/+1
|
* Changed only_preliminaries to for_accounts_reportJohn Wiegley2009-11-182-5/+5
|
* Added an ACCOUNT_GENERATED flagJohn Wiegley2009-11-181-3/+4
|
* Allow ! and - operators on sequence valuesJohn Wiegley2009-11-181-0/+14
|
* Wasn't serializing date_range_t::end_inclusive memberJohn Wiegley2009-11-181-0/+1
|
* Guarded some debug codeJohn Wiegley2009-11-181-0/+2
|
* The new period parser is passing all testsJohn Wiegley2009-11-188-146/+214
|
* The new period parser is implemented, but untestedJohn Wiegley2009-11-183-629/+883
|
* Added a "range" member to date_interval_tJohn Wiegley2009-11-182-30/+34
| | | | | | This is used to define the beginning/ending ranges of the time period, before it becomes fixed (by calling stabilize()) and then sets the values of start and end.
* Added several new types for working with dates and rangesJohn Wiegley2009-11-172-0/+615
| | | | | | | | | | | | | | | | | | | | | | | | date_specifier_t :: This is like a plain date_t, except it knows what wasn't specified. For example, if 2008/06 is parsed, it becomes date_specifier_t which knows that no day was given. If you ask for the begin() date of the specifier, it will be 2008/06/01; the end() date (which is exclusive) will be 2008/07/01. date_range_t :: A date range is a range of two specifiers, either of which (but not both) may be omitted. This makes it possible to represent expressions like "from june to july", where no day or year is given. The exact dates will be inferred by using the current year, and fixing the range from YEAR/06/01 to YEAR/07/01. That is, the range goes from the begin() of one date specifier to the begin() of the other. date_specifier_or_range_t :: A variadic type that can be either a date_specifier_t or a date_range_t. It's just a wrapper to represent the fact that ranges can be implicit via specifiers (such as, "in june"), or explicit via ranges ("since 2008").
* Moved date_interval_t::duration_t to date_duration_tJohn Wiegley2009-11-172-108/+106
|
* Added a date_traits_t typeJohn Wiegley2009-11-172-26/+68
|
* Renamed date_interval_t::end to finishJohn Wiegley2009-11-176-52/+52
|
* Some reformatting in query.hJohn Wiegley2009-11-171-35/+37
|
* Added ledger::string(Iter, Iter) constructorJohn Wiegley2009-11-171-0/+5
|
* Fixed several time and date duration type usesJohn Wiegley2009-11-172-9/+16
|
* Made the account and tag directives more rationalJohn Wiegley2009-11-151-69/+81
| | | | | Now you must specify "account / end account", and "tag / end tag". For backwards compatability, plain "end" is the same as "end account".
* Corrected parsing of the 'expr' report query termJohn Wiegley2009-11-152-10/+14
|
* Made the transaction date parser a bit more strictJohn Wiegley2009-11-151-10/+13
|
* Made the amount_t::bigint_t refcount holder 32-bitsJohn Wiegley2009-11-141-6/+2
| | | | It was overflowing on a full register report of just 3M of data.
* Changed a use of balance_error to amount_errorJohn Wiegley2009-11-141-1/+1
|
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-10 10:16:34 +0000