| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Windows uses UTF-16 for command line arguments, so use boost::nowide
to convert to UTF-8.
Fixes #1986
|
|
|
|
|
| |
Windows doesn't seem to use UTF-8 by default, so we can specify
encoding='utf-8'. Also, backslashes are confusing to regex parsers.
|
| |
|
|
|
|
| |
Date format %F is not available on all platforms.
|
|
|
|
| |
Useful for building in a MINGW32/64 console on Windows.
|
| |
|
|
|
|
| |
Fixes #1905
|
|
|
|
|
| |
Payees declared on posting's metadata are now validated with `--check-payees`
option. Also, their aliases are now considered on reports as well.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This changes the error reported when a transaction with no amount is
imported.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
also add unit tests
|
|
|
|
| |
Fix shellcheck warning SC2034: command appears unused.
Fix completion script if used by zsh with bashcompinit.
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Fixes #1963
|
|
|
|
| |
Fixed #1954
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
Added instructions to install build dependencies in Fedora 32.
|
|
|
|
|
|
|
| |
Document how to pass multiple debug flags to ledger using a regular
expression.
Fixes #1062
|
|
|
|
|
| |
`$XDG_CONFIG_HOME/ledger/ledgerrc` and `$HOME/.config/ledger/ledgerrc`
are tried first when looking for an init file.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
`l` does not exist anymore, the account depth is available as `depth`.
|
|
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
|
|
| |
The temps will not have correct depth information attached which means
a display predicate involving `depth` will most likely lead to wrong
results.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Use the value from --depth as the collapse_depth for --collapse.
|
|
|
|
|
| |
Replace the hardcoded depth of 3 with a class attribute that can later
be set from a commandline argument.
|
| |
|
|
|
|
|
| |
The current one doesn't work; also Ledger has got a much neater
command-line option to achieve the goal.
|
|
|
|
|
|
|
|
|
|
| |
The PDF manual used UTF-8 quotes like:
expr has_tag(’TAG’)
which isn't accepted by ledger.
Fixes #1898
|
|
|
|
|
|
|
| |
The code looked for "less" if $PAGER is not set, but it didn't
actually use $PAGER when it it defined.
Fixes #1674
|
|
|
|
|
| |
Without this fix, the Nix build is broken, which causes `ledger-mode` CI builds to fail.
See https://github.com/NixOS/nixpkgs/commit/887295fd2d8c4da06acdaa185cbb3cc214d83285
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|