summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Fix compilation with Boost 1.76Sam James2021-06-142-0/+4
| | | | | | | | We were previously relying on an indirect include within Boost headers. We're using scoped_ptr which is defined in <boost/smart_ptr/scoped_ptr.hpp>. Bug: https://bugs.gentoo.org/790176 Closes: https://github.com/ledger/ledger/issues/2030
* Remove reference to FreenodeMartin Michlmayr2021-06-071-1/+1
| | | | Fixes #2035
* Update IRC to Libera ChatMartin Michlmayr2021-06-023-3/+3
|
* Escape all string values output by the lisp report.Richard M Kreuter2021-05-311-6/+6
| | | | | | | Notes were already being escaped. The filename, the transaction code, the payee,, postings' account names, and postings' cost expressions were not. Everything else the lisp report prints appears to be a number or a constant-valued non-string token for Lisp.
* Show "FAILURE in exit code" when success is expectedAlan Bram2021-05-041-5/+4
| | | | Fixes #2023.
* Fix amount tokenizer re: embedded minus sign.Donald Lam2021-05-022-2/+21
| | | | | An amount may have a (single) leading minus sign, but none after that. Bug #2001 (and #1809).
* Fix IRC bullet point in README.md🎷🐛 Cat Lee Ball2021-04-191-1/+1
| | | | | | | | | | | | Currently the IRC link is broken in the rendered readme page on Github. Speculating that Github's markdown renderer might not display the text as a link since it starts with "irc://" instead of "http://" or similar. Added some text to the bullet point specifying channel and server. I left the link in-place in case the above issue is resolved at some point, or if other websites render this README.md file without the issue.
* Fix using day-of-week names for `xact` commandAlan Bram2021-04-102-13/+36
| | | | Also fix end-of-command boundary checks for keywords "at", "to", etc.
* Remove obsolete mention of Cheetah web framework.Alan Bram2021-04-071-3/+0
| | | | | | The "python/server.py" file was removed with fix for #1759. [ci skip]
* Refer to the right amount used in the exampleŁukasz Stelmach2021-03-151-1/+1
|
* Fix .yamllintMartin Michlmayr2021-02-021-2/+5
| | | | The yamllint config file was incorrect.
* Use Boost library to read argv as UTF-8 in WindowsDaniel Coonce2021-02-023-1/+16
| | | | | | | Windows uses UTF-16 for command line arguments, so use boost::nowide to convert to UTF-8. Fixes #1986
* Make test harness more Windows compatibleDaniel Coonce2021-02-023-17/+18
| | | | | Windows doesn't seem to use UTF-8 by default, so we can specify encoding='utf-8'. Also, backslashes are confusing to regex parsers.
* Have acprep use system encoding for stdin/outDaniel Coonce2021-02-021-2/+3
|
* Don't use date format %FDaniel Coonce2021-02-021-1/+1
| | | | Date format %F is not available on all platforms.
* Add support for MSYS Makefiles in acprepDaniel Coonce2021-02-021-0/+3
| | | | Useful for building in a MINGW32/64 console on Windows.
* Create consistent buffer size.Daniel Coonce2021-02-022-2/+2
|
* Fix build for x86_64-w64-mingw32Daniel Coonce2021-02-023-4/+4
| | | | Fixes #1905
* Fix issues related to payees declared on posting's metadataDiogo Trentini2021-02-028-30/+87
| | | | | Payees declared on posting's metadata are now validated with `--check-payees` option. Also, their aliases are now considered on reports as well.
* Add example of single-column CSV importKai Wohlfahrt2021-01-311-0/+10
|
* Replace if/else ladder in convert with loopKai Wohlfahrt2021-01-312-41/+19
|
* Update documentation for new convert featuresKai Wohlfahrt2021-01-311-20/+23
|
* Add debit field to convert commandKai Wohlfahrt2021-01-315-9/+45
| | | | | This changes the error reported when a transaction with no amount is imported.
* compare_by_commodity: Always return the result of the recursive callChristoph Dittmann2021-01-302-6/+25
| | | | | | | | | | | | | | | | | | | | | | | Commit 501fbc08ae5493db77bb34f4c4fbe1f3a3bc14e3 changed the behavior of this function to not return the "equal" result (==0) from the recursive call. Previously, the function returned the result of the recursive call unconditionally. The current behavior causes an assertion error for certain postings. The regression test added in this commit shows such a posting. I found through Travis CI that the old behavior was incomplete and caused unstable orderings, so reverting to the old behavior doesn't work. Instead, this change adds a fallback: If the recursive call that compares the prices numerically returns "equal", then compare the prices with their original commodity as a tie breaker. This commit does not change any existing ordering, it only adds deterministic ordering in a case that currently triggers an assertion error. This fixes issue #1998.
* format_t::truncate support wide charactersKuang-che Wu2021-01-174-11/+181
| | | | also add unit tests
* Fix contrib bash-completionmst2021-01-171-1/+1
| | | | Fix shellcheck warning SC2034: command appears unused. Fix completion script if used by zsh with bashcompinit.
* Support for building on older cmake versionsSanel Zukan2021-01-141-2/+3
| | | | | | | | Backported python cmake module expects at least cmake 3.7 (requested by policy), which will break builds on older cmake versions, like 3.5. This fix will omit python module inclusion for any cmake version less than 3.7 and the build will continue without problems.
* docs: add more value expressionsMartin Michlmayr2020-12-311-0/+12
|
* Do not treat balance assignments with 0 diff as a null postingDaraul Harris2020-12-055-1/+117
| | | | | | | | | | | Ledger is treating balance assignments that have a 0 diff as having a null posting, leading to the posting being auto-balanced and therefore causing incorrect values to be returned for the transaction. I fixed this by just making the posting equal to amt - amt (0 in the right commodity). Fixes #1942
* docs: add link to relevant sectionMartin Michlmayr2020-11-101-1/+1
| | | | Fixes #1963
* docs: clarify syntax of ~/.ledgerrcMartin Michlmayr2020-11-101-0/+1
| | | | Fixed #1954
* Fix regression in sorted_amountsMartin Michlmayr2020-10-302-1/+19
| | | | | | | | | | Commit 557ab32 ("Expose a new utility function for balances: sorted_amounts") split out some code into a separate function. Unfortunately, in the process an "if" statement was dropped, leading to amounts being shown that shouldn't be shown because they are smaller than the display precision. Fixes #1969
* default.nix: Fix testingMichael Raitza2020-10-301-2/+5
|
* Implement cryptographic access to files using GPGMEMichael Raitza2020-10-309-8/+401
|
* Add .yamllintMartin Michlmayr2020-10-301-0/+2
|
* Fix typo in ledger3.texiKuang-che Wu2020-10-131-1/+1
|
* Added Fedora build dependencies to README.mdMarin BERNARD2020-10-041-0/+10
| | | Added instructions to install build dependencies in Fedora 32.
* Document how to specify multiple debug flagsDaraul Harris2020-09-251-2/+3
| | | | | | | Document how to pass multiple debug flags to ledger using a regular expression. Fixes #1062
* Add support for `$XDG_CONFIG_HOME`Cédric Barreteau2020-08-284-18/+28
| | | | | `$XDG_CONFIG_HOME/ledger/ledgerrc` and `$HOME/.config/ledger/ledgerrc` are tried first when looking for an init file.
* Fix whitespace/tabsEmin Martinian2020-08-131-6/+6
|
* Make it so that the include directive sorts when using wildcards.Emin Martinian2020-08-131-4/+12
| | | | | | | | Before this commit, doing something like 'include data/*.dat' would produce undesired behaviour because the matches for 'data/*.dat' would not be sorted correctly. See https://github.com/ledger/ledger/issues/1659 for details.
* docs: fix quotation mark in man pageMartin Michlmayr2020-08-101-1/+1
|
* docs: Document new --depth in register reportsRahix2020-07-212-2/+7
|
* docs: Fix documentation for `depth`Rahix2020-07-211-1/+1
| | | | `l` does not exist anymore, the account depth is available as `depth`.
* Treat --depth like --collapse in registerRahix2020-07-211-1/+1
| | | | | | | | | | Currently, collapsing is only done when both --depth and --collapse are present. This is very unintuitive and I have even stumbled over this myself while implenting the feature. Change --depth to behave just like --collapse in all cases (except that --depth has a parameter associated. --collapse defaults to 0 to retain its old behavior).
* collapse_posts: Use the existing accounts instead of tempsRahix2020-07-212-4/+12
| | | | | | The temps will not have correct depth information attached which means a display predicate involving `depth` will most likely lead to wrong results.
* collapse_posts: Fix some postings getting lost when collapsingRahix2020-07-211-1/+1
| | | | | | | | | | Because the only_predicate and display_predicate are applied to the original posts, not the collapsed ones, they sometimes yield wrong results leading to entire transactions getting dropped erroneously. As this code is only relevant to depth == 0 collapsing (that is, the old behavior), only follow the displayed_count == 1 code-path when the depth is 0.
* collapse_posts: Fix segfault when depth is too bigRahix2020-07-211-1/+1
| | | | | | | When an account already has less depth than collapse_depth, a segfault was caused by attempting to move up the account parents until parent is NULL. Fix this by exiting early if the depth is already less than collapse_depth.
* collapse_posts: Use --depth as the collapse_depthRahix2020-07-211-2/+8
| | | | Use the value from --depth as the collapse_depth for --collapse.
* collapse_posts: Add a collapse_depth attributeRahix2020-07-212-6/+7
| | | | | Replace the hardcoded depth of 3 with a class attribute that can later be set from a commandline argument.