summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Abstracted an sha1sum() functionJohn Wiegley2010-03-062-6/+11
|
* Fixed a problem with the "quoted" valexpr functionJohn Wiegley2010-03-051-2/+2
|
* Added some preliminary code for convert CSV to LedgerJohn Wiegley2010-03-056-2/+445
|
* Added new "payee" and "capture" directivesJohn Wiegley2010-03-053-1/+62
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The payee directive allows for transformation of payee names during the parsing of a Ledger file. This means you can record the payee name in one form, but always have it reported in another form. The syntax is (and will be): payee PAYEE_NAME REGEXP or payee PAYEE_NAME REGEXP1 REGEXP2 ... The account directive sets the account automatically based on the payee iff the base account name is Unknown. For example, if you have a bunch of transaction in Expenses:Unknown, you can assign accounts for several automatically using: account ACCOUNT_NAME PAYEE_REGEXP or account ACCOUNT_NAME PAYEE_REGEXP1 PAYEE_REGEXP2 ...
* Change an exception test to a plain ifJohn Wiegley2010-03-051-4/+2
|
* Updated copyrights to 2003-2010John Wiegley2010-03-05115-116/+116
|
* Renamed the "args" command to "query"John Wiegley2010-03-043-3/+7
|
* Some minor refactoring of the textual parserJohn Wiegley2010-02-053-176/+145
|
* Reformatted a commentJohn Wiegley2010-02-051-3/+2
|
* Added post_t::compare_by_date_and_sequence comparatorJohn Wiegley2010-02-051-0/+14
|
* Refactored some comparison helper classesJohn Wiegley2010-02-054-8/+9
|
* Added actual_date() methods for itemsJohn Wiegley2010-02-054-0/+22
|
* Added a "seq" sequence property for all itemsJohn Wiegley2010-02-043-20/+39
| | | | | This indicates the absolute parsing order of every transaction and posting. It is 0 for generated items.
* Improved the behavior of pivot reportsJohn Wiegley2010-02-041-12/+19
|
* Added a --pivot=TAG optionJohn Wiegley2010-02-024-6/+48
| | | | | | This is equivalent to the following: --account='"TAG:" + tag(/TAG/)'
* When creating temporary accounts, transfer flagsJohn Wiegley2010-02-021-1/+7
|
* Added a debug statement for report.predicateJohn Wiegley2010-02-021-2/+5
|
* Fixed assertion failure in -M -A bal reportJohn Wiegley2010-01-211-1/+1
|
* Guard against divide by zero error in -A reg reportJohn Wiegley2010-01-211-1/+1
|
* Fixed account display bug in the balance reportJohn Wiegley2010-01-211-5/+4
|
* Restore "-p this" option (aka -p 'this month')John Wiegley2010-01-211-11/+7
|
* 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.
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-08 17:17:36 +0000