summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* New command: org, for displaying Org-mode tablesJohn Wiegley2010-12-223-0/+304
|
* Added "top_amount" value expr functionJohn Wiegley2010-12-222-0/+25
|
* Create format_t::mark_uncompiledJohn Wiegley2010-12-222-2/+11
|
* Whitespace fixJohn Wiegley2010-12-221-1/+0
|
* Increase display precision of hours to 2 placesJohn Wiegley2010-12-121-1/+1
|
* Parse %m/%d/%Y %H:%M:%S as an input date/timeJohn Wiegley2010-12-041-2/+9
| | | | This is to support reading of Timelog files.
* Corrected syntax errors found by ClangJohn Wiegley2010-10-072-6/+8
|
* Made -> have higher precedence than commaJohn Wiegley2010-09-061-26/+26
|
* Added initial support for lambda functionsJohn Wiegley2010-09-066-27/+129
|
* Minor simplifications to valexpr parserJohn Wiegley2010-09-0510-96/+79
| | | | | The most significant change is the way CONS sequences are parsed, and that now instead of =/:=, the operators are ==/=.
* Moved up to Boost 1.44John Wiegley2010-08-242-1/+9
|
* Based symbol_needs_quotes an invalid_chars (#386)John Wiegley2010-07-291-32/+32
|
* Boost.Python fixes now that item_t is abstractJohn Wiegley2010-07-292-2/+2
|
* The "source" command now accepts code from stdinJohn Wiegley2010-06-261-0/+2
|
* The "print" valexpr function no longer adds spacesJohn Wiegley2010-06-261-9/+2
|
* Move balance divider right by prepend-widthJohn Wiegley2010-06-261-0/+3
|
* Added "format" value expression functionJohn Wiegley2010-06-242-0/+11
| | | | | | | | | This function evaluates formatting strings, returning a string. For example: format("%(amount)") This is equivalent to "to_string(amount)".
* Generalized the semantics of FOO.BAR in valexprsJohn Wiegley2010-06-241-17/+7
| | | | | | | | | | | | | Previously, FOO was evaluated to return a scope, and BAR was an identifier looked up in that scope. However, this prevented scope-local functions from being called (since that is a CALL, not a plain IDENT). Now the meaning of the "." operator is that it evaluates the left operand in a scope type context, pushes that scope as the current object context, and then evaluates BAR in that context. Thus the bare word "amount" in an account context calls the same function that "account.amount" would if evaluated in a posting context.
* Added "source" command, for executing valexpr filesJohn Wiegley2010-06-243-0/+30
|
* Fixed how valexpr function defs and calls workJohn Wiegley2010-06-241-15/+32
|
* Scopes can now provide a description of themselvesJohn Wiegley2010-06-248-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 chainingJohn Wiegley2010-06-242-16/+9
|
* "only" now a report query modifier for --onlyJohn Wiegley2010-06-243-20/+31
| | | | This fits with "show" and "bold", etc.
* Added report query modifiers: for, since, untilJohn Wiegley2010-06-225-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".
* Price annotation no longer inject an implied costJohn Wiegley2010-06-221-21/+7
| | | | | | | | | | | | | | | | | | | | | | | 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 xactsJohn Wiegley2010-06-221-48/+50
|
* Added has_date() method to item_tJohn Wiegley2010-06-221-0/+4
|
* The notions of "now" and "today" now use local timeJohn Wiegley2010-06-221-3/+3
|
* Added new "bold" modifier to query expressionsJohn Wiegley2010-06-227-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'
* Added new --bold-if optionJohn Wiegley2010-06-222-16/+59
|
* Balances and sequences can be compared to amountsJohn Wiegley2010-06-221-16/+4
|
* bal was sometimes reporting empty accountsJohn Wiegley2010-06-213-6/+14
|
* Change weighting of account-name abbreviationJohn Wiegley2010-06-211-1/+1
| | | | | Parent accounts are abbreviated even more, so that child accounts can show more text.
* Corrected a major flaw in the transaction finalizerJohn Wiegley2010-06-211-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 parsingJohn Wiegley2010-06-211-8/+190
| | | | | Things like "since last month" and "4 weeks ago", and "since 4 weeks ago" are now all working.
* Corrected a compilation warningJohn Wiegley2010-06-211-2/+3
|
* Transactions no longer needed for budget/forecastJohn Wiegley2010-06-201-4/+6
| | | | | This means you can forecast or budget against a file containing only periodic transactions.
* Output budget even if no postings directly matchedJohn Wiegley2010-06-202-4/+2
|
* Added missing call to resolve_end() in find_periodJohn Wiegley2010-06-201-0/+2
|
* Factored out some unused local variablesJohn Wiegley2010-06-201-9/+5
|
* Rename dow_posts to day_of_week_posts, to be clearerJohn Wiegley2010-06-203-10/+10
|
* If fixated price commodities are mixed, show themJohn Wiegley2010-06-203-23/+62
| | | | | | | | | | | 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 itJohn Wiegley2010-06-201-25/+33
|
* --input-date-format now affects dates with timesJohn Wiegley2010-06-201-1/+8
|
* Do not record market values for fixated exchangesJohn Wiegley2010-06-201-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.
* When anonymizing posts, remove the transaction codeJohn Wiegley2010-06-201-0/+1
|
* Added debug print for commodity.prices.findJohn Wiegley2010-06-201-0/+2
|
* If a periodic posting terminates, stop forecasting with itJohn Wiegley2010-06-201-4/+5
|
* Subsantial fixes and improvements to budgetingJohn Wiegley2010-06-193-11/+48
| | | | | | | | | 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.
* Corrected a bug in report query parsingJohn Wiegley2010-06-191-2/+2
|
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-06 15:06:07 +0000