summaryrefslogtreecommitdiff
path: root/src/textual.cc
Commit message (Collapse)AuthorAgeFilesLines
* For Boost 1.35 and earlier, use is_regularJohn Wiegley2010-05-231-1/+6
| | | | Fixes 0F17CB7F-A000-4F99-8471-739948AD575F
* Corrected handling of context stack in the parserJohn Wiegley2010-05-221-23/+8
| | | | Fixes F4A477E6-C4F6-43B1-ABCC-4DC325C2869A
* Guard against NULL value passed to "end" directiveJohn Wiegley2010-05-221-1/+1
| | | | Fixes 89233B6D-CB21-4162-98E3-BE38B9336070
* The include directive now supports file globbingJohn Wiegley2010-03-171-5/+33
| | | | | This only happens at the base filename, not for any of the directory names for now.
* Tags were not being set properly on postingsJohn Wiegley2010-03-171-4/+4
|
* Extended regexp syntax for "payee" and "capture"John Wiegley2010-03-101-4/+32
|
* Rewrite the "print" command as a custom functionJohn Wiegley2010-03-081-0/+1
| | | | | There ended up being too many corner cases for the generalized formatter to handle.
* Added new "payee" and "capture" directivesJohn Wiegley2010-03-051-1/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 ...
* Updated copyrights to 2003-2010John Wiegley2010-03-051-1/+1
|
* Some minor refactoring of the textual parserJohn Wiegley2010-02-051-176/+129
|
* Added a "seq" sequence property for all itemsJohn Wiegley2010-02-041-19/+28
| | | | | This indicates the absolute parsing order of every transaction and posting. It is 0 for generated items.
* Cost of a post with neg. amount should be negativeJohn Wiegley2009-12-071-0/+3
|
* Allow relative includes in the current directoryJohn Wiegley2009-12-071-4/+10
|
* Added support for a "fixed" directiveJohn Wiegley2009-11-251-10/+59
| | | | | | | | | | | | | | | | | | | 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
* * and | now comment chars, for the sake of Org-modeJohn Wiegley2009-11-251-2/+4
|
* Many improvements to Ledger's Python bindingsJohn Wiegley2009-11-191-3/+3
|
* 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".
* Did away with the "finalizer" abstractionJohn Wiegley2009-11-111-12/+1
| | | | | This was from an earlier time, when it was intended to be used by Python. But it's not needed anymore.
* Automated postings defer amount expression calculationJohn Wiegley2009-11-111-30/+45
| | | | | | | | | | | | | | | | | This allows for value expressions to be used which reference the incoming posting, for example: = Income:Clients: (Liabilities:Taxes:VAT1) (floor(amount) * 1) (Liabilities:Taxes:VAT2) 0.19 2009/07/27 * Invoice Assets:Bank:Checking $1,190.45 Income:Clients:ACME_Inc The automated posting for VAT1 will use the floored amount multiplied by a factor, while the posting for VAT2 multiples the whole amount as before.
* Timeclock events now record their file positionJohn Wiegley2009-11-111-5/+25
|
* Timeclock entries can now have notesJohn Wiegley2009-11-111-4/+18
| | | | | | | | | | Example of a tagged entry: i 2009/11/01 12:00:00 Account Payee ; :Foo: o 2009/11/01 13:00:00 Two spaces or a tab must separate account from payee, and payee from note.
* Fixed an erroneous use of operator>> in textual.ccJohn Wiegley2009-11-101-1/+1
|
* Automated transactions now use report query syntaxJohn Wiegley2009-11-101-2/+3
| | | | This returns their behavior back very close to what 2.x accepts.
* Corrected the parsing of data file directivesJohn Wiegley2009-11-101-9/+15
|
* Added "bucket" directive, as alt for AJohn Wiegley2009-11-101-6/+13
|
* Support include-ing of relative pathnamesJohn Wiegley2009-11-101-1/+11
|
* It's now an error to use "end" without "account"John Wiegley2009-11-101-2/+2
|
* Directives no longer require @ or ! prefix charJohn Wiegley2009-11-101-59/+62
|
* Throw an exception if an include file doesn't existJohn Wiegley2009-11-101-0/+4
|
* Redesigned the expr_t, predicate_t, query_t classesJohn Wiegley2009-11-091-19/+15
|
* Throw an error for unrecognized options in data filesJohn Wiegley2009-11-071-11/+2
|
* Renamed journal_t::basket to bucketJohn Wiegley2009-11-071-2/+2
|
* Segregated symbols into 5 separate namespacesJohn Wiegley2009-11-041-8/+6
| | | | | | | | | | | | | | | | | | | | | The different namespaces are: Function Value expression functions, which receive a "context" Option Command-line options Precommand Commands which are invoked before reading the journal Command Commands which are invoked after reading the journal Directive Directives that occur at column 0 in a data file This greatly eases the ability for Python uses to add intercept hooks to change how the basic Ledger module functions. An example of what should be possible soon: import ledger def my_foo_handler(value): print "--foo received:", value ledger.add_handler(ledger.Option, "foo=", my_foo_handler)
* Fix to xact_t::valid()John Wiegley2009-11-011-0/+3
|
* Commented out dependency on session_t (for now)John Wiegley2009-10-311-0/+4
|
* Removed most #if 0 blocks and callout commentsJohn Wiegley2009-10-311-18/+1
|
* Add a position_t object for tracking item positionsJohn Wiegley2009-10-301-25/+29
| | | | It is also optional, which is useful for generated items.
* Setting --date-format in ~/.ledgerrc works againJohn Wiegley2009-10-291-15/+23
|
* Further improvements to handling temporariesJohn Wiegley2009-10-281-14/+1
|
* Renamed two methods, for consistency's sakeJohn Wiegley2009-10-271-1/+1
|
* Redid the way temporaries are handled in filteringJohn Wiegley2009-10-271-3/+3
|
* Balance assertions now really assertJohn Wiegley2009-10-261-17/+25
| | | | | | | | There are two kinds of balance related options for a posting: a balance assignment, where the amount of the posting is blank and so it fills it in to make the assertion true; and plain assertions, where the amount is not blank and an error is reported if the balance does not match the given amount after the posting is taken into account.
* If a pricing entry fails to parse, give an errorJohn Wiegley2009-10-261-1/+2
|
* Removed reliance on strptime/strftimeJohn Wiegley2009-10-111-2/+3
| | | | | | | | The code now uses Boost's input and output facets for times and dates. This ensures completely consistency regarding timezones and times, and fixes the regression test that was broken while I was away coding in London (where it was GMT-0 and I didn't notice the difference between local and GMT).
* Split commodity.h/cc into three filesJohn Wiegley2009-06-241-1/+2
| | | | | | commodity.h - code for commodity_t annotate.h - commodity annotations pool.h - commodity pool management
* Restored --download, although not done yetJohn Wiegley2009-06-241-53/+4
| | | | | | The problem at this point is that it's recording prices in the price database multiple times; it should only need to download a price for each commodity once per day.
* Allow uncommoditized amounts to be used as costsJohn Wiegley2009-06-181-1/+7
|
* Fixed a problem with accounts and trailing spacesJohn Wiegley2009-06-161-0/+3
| | | | | | | This issue is caused by having a single space at the end of a posting that has neither an amount nor a note. Fixes C523E23F-CFAC-4A53-B0C6-21226640E763
* Strip annotations before handling bal assignmentsJohn Wiegley2009-06-131-1/+2
|
* Added new debug option --optionsJohn Wiegley2009-06-021-1/+1
| | | | | This reports which options are in place before invoking a command, and where exactly each option value came from.
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-08 17:29:15 +0000