| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
`l` does not exist anymore, the account depth is available as `depth`.
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes #1877
|
| |
|
|
|
|
| |
Fixes #1690
|
| |
|
|
|
|
| |
Fixes #1868
|
|
|
|
|
|
|
| |
This change adds a warning in the documentation for users using
automated transactions with `--strict` or `--pedantic`, as ledger
will throw an error when `$account` is not defined explicitly
(see #545).
|
|
|
|
|
| |
and add some cross references to more detailed documentation and
examples.
|
| |
|
|
|
|
|
|
| |
Currently the docs recommend the use of balance --average to help
generate a budget. Apparently that doesn't work. Instead use the
register command with --average.
|
|
|
| |
Common misspelling of aforementioned.
|
|
|
|
|
|
|
|
|
| |
'%F' is equivalent to '%Y-%m-%d'. Using the '%F' format without this
change this would not give any hard errors but instead give dates with
wrong years because the 'has_year' trait would not be correctly
detected and thus parsed dates would get set to the current year.
Fixes #1775
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
If a tag is more than 2 characters from the beginning of the comment the
tag value offset will be wrong. #1702 gives an example where the tag
line starts with `;;` and the tag value thus becomes `: Bar` because of
this bug.
The use `index` in the offset calulation seems to be a lucky coincidence
that works in the common case: "; tag: value"
Fixes #1702
|
|
|
|
| |
Fixes #1753
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
fix "Income increases with credits"
|
| |
| |
| | |
Signed-off-by: Georg J.P. Link <linkgeorg@gmail.com>
|
|/
|
| |
Signed-off-by: Georg J.P. Link <linkgeorg@gmail.com>
|
| |
|
| |
|
|
|
|
|
|
| |
Thanks to Alexis Hildebrandt.
Fixes #1763
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When using the `--gain` option the `temporaries_t` in
`changed_value_posts` filter stores a reference to the `<Revalued>` temp
account created in `display_filter_posts`. When destroying the filter
chain `display_filter_posts` is destroyed before `changed_value_posts`
and this can result in a use-after-free in `temporaries_t::clear()` when
`temps` in `changed_value_posts` is cleared during destruction if there
are any temp posts referencing the `<Revalued>` account.
Fix the issue by clearing the `temporaries_t` in `changed_value_posts`
before destroying the rest of the filter chain (which includes
`display_filter_posts`).
Fixes #541
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is possible to create a stack overflow by giving an option that is
longer than the buffer that is used during option parsing because the
length of the input string is not checked.
Prevent the issue by always checking the input string length and
discarding options that does not fit in the buffer as invalid.
This issue has been assigned CVE-2017-12481.
Thanks to Gwan Yeong Kim for reporting this issue.
Fixes #1222
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is possible to create a stack overflow by giving a date that is
longer than the buffer that is used during date parsing because the
length of the input string is not checked. The `VERIFY` macro is only
enabled when debug-mode is enabled and the `--verify-memory` argument is
used.
Prevent the issue by always checking the input string length and
discarding dates that does not fit in the buffer as invalid.
This issue has been assigned CVE-2017-12482.
Fixes #1224
|