summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge remote branch 'kljohann/vim' into nextJohn Wiegley2010-11-093-108/+336
|\
| * vim. highlight typed tagsJohann Klähn2010-10-071-2/+4
| | | | | | | | | | See mailing list on June 12 2010 / "New: Support for typed metadata" Message-Id: <D22C04C4-64F7-49B9-8006-2F7F97A4298A@gmail.com>
| * vim. parse comments at eol in parse_body()Johann Klähn2010-09-151-13/+18
| |
| * vim. highlight metadata on same line as postingJohann Klähn2010-09-151-1/+1
| |
| * vim. fix off-by-one bug in ToggleTransactionStateJohann Klähn2010-09-151-1/+1
| |
| * vim. fix issue with description in from_lnum()Johann Klähn2010-09-151-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | Thanks to Chad Voegele, see mailing list ledger-cli@googlegroups.com: Whenever I had a transaction such as 2010/09/10 * castle bar, nyc (beer) the transaction.from_lnum function would recognize (beer) as the code for the transaction which is incorrect since it comes at the end of the line. Message ID: 73e397f4-234e-46fe-87e5-45f86f934bf1@k30g2000vbn.googlegroups.com
| * vim. fix highlighting of comments at end of lineJohann Klähn2010-09-131-1/+2
| |
| * vim. change syntax file to allow comments at eolJohann Klähn2010-09-131-31/+24
| |
| * vim. remove tag completion for nowJohann Klähn2010-09-121-64/+5
| |
| * vim. avoid misinterpretion of 1 char wordsJohann Klähn2010-09-121-1/+1
| |
| * vim. check for most common case first (parse_body)Johann Klähn2010-09-081-7/+7
| |
| * vim. add LedgerToggleTransactionState()Johann Klähn2010-09-081-6/+31
| | | | | | | | | | | | | | | | | | | | | | By using call LedgerToggleTransactionState(line('.'), ' *?') the state of the transaction will toggle through: no state -> * -> ? -> no state -> … beginning at what ever state it currently has. Adjust to your liking. Thanks to Chad Voegele for the suggestion.
| * vim. make sure cursor/line is on a transactionJohann Klähn2010-09-081-0/+5
| | | | | | | | | | Thanks to Chad Voegele for reporting and fixing this in the first place.
| * vim. update s:get_columns()Johann Klähn2010-09-081-8/+16
| |
| * vim. get transactions in a range of linesJohann Klähn2010-09-081-0/+35
| |
| * vim. fix return type of s:transaction.from_lnum()Johann Klähn2010-09-081-2/+2
| |
| * vim. add function to parse postingsJohann Klähn2010-09-081-0/+75
| |
| * vim. add case of automatic transactionsJohann Klähn2010-09-081-2/+17
| |
| * vim. reimplement function to change stateJohann Klähn2010-09-081-1/+14
| | | | | | | | | | Note: You now have to provide the line number: call LedgerSetTransactionState(line('.', '*')
| * vim. allow use of 0 as timestampJohann Klähn2010-09-081-1/+1
| | | | | | | | | | To remove the effective date you would now call the function like this: call LedgerSetDate(line('.'), 'effective', -1)
| * vim. add function to modify actual/effective dateJohann Klähn2010-09-081-0/+35
| | | | | | | | | | | | | | This allows you to set the effective date in a convenient way. Maybe I will add date selection using calendar.vim by Yasuhiro Matsumoto. Until then, you can map this to use today's date: call LedgerSetDate(line('.'), 'effective')
| * vim. introduce basic transaction 'class'/conceptJohann Klähn2010-09-081-27/+54
| |
| * vim. add function to change item state ~ reconcileJohann Klähn2010-09-071-0/+35
| | | | | | | | | | | | | | | | | | | | | | To try this, map or call the following function: LedgerSetTransactionState('') – removes state LedgerSetTransactionState('*') – sets 'checked' state … The logic used to distinguish the different parts of the first line of a transaction is rather basic but proved to work so far.
| * vim. use ledger print as 'formatprg'Johann Klähn2010-09-072-7/+18
| | | | | | | | | | You can now try to select some lines using V (visual mode) and have them automatically formatted using gq
| * vim. display warning messages in quickfix windowJohann Klähn2010-08-141-2/+3
| | | | | | | | | | To use this option you must set g:ledger_bin = "ledger --strict" before the compiler plugin is loaded (your .vimrc for example).
* | Added acprep support for building with ClangJohn Wiegley2010-10-072-51/+81
| |
* | Corrected syntax errors found by ClangJohn Wiegley2010-10-072-6/+8
| |
* | Removed extraneous semicolons from utfcppJohn Wiegley2010-10-061-0/+0
| |
* | 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-245-5/+19
| |
* | Added regression test for 7C44010BJohn Wiegley2010-08-161-0/+30
| |
* | Added regression test for 9EB10714John Wiegley2010-08-161-0/+43
| |
* | Corrected syntax error in new ledger3 docMartin Michlmayr2010-07-301-9/+9
| |
* | Based symbol_needs_quotes an invalid_chars (#386)John Wiegley2010-07-292-32/+41
| |
* | Boost.Python fixes now that item_t is abstractJohn Wiegley2010-07-292-2/+2
| |
* | Updated README-1ST fileJohn Wiegley2010-07-021-14/+9
| |
* | Added baseline test for "check" featureJohn Wiegley2010-06-261-0/+18
| |
* | 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
| |
* | Added baseline tests for --meta and --meta-widthJohn Wiegley2010-06-262-0/+28
| |
* | Added baseline test for --nowJohn Wiegley2010-06-261-0/+4
| |
* | Added baseline tests for prepend-format/widthJohn Wiegley2010-06-262-0/+34
| |
* | 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.
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-09 08:21:56 +0000