| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |\ \ \ \ \ \ \
| | |/ / / / / /
| |/| | | | | | |
build fixes for boost 1.58
|
| | | | | | | | |
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
Instead we use boost::none, which has been documented since boost 1.34.0.
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Don't explicitly link libpython on OS X
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Use -undefined dynamic_lookup to allow Python symbols to be discovered
when the ledger module is imported instead of at build time. Without
this change, the Python interpreter crashes when ledger is imported from
a python that is different from (but compatible with) the python against
which the module was built.
|
|\| | | | | | |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Use ./.ledgerrc if ~/.ledgerrc doesn't exist
|
| |/ / / / / / |
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Improve baseline tests
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
--generated will generate each time new entries, this cannot be
reproduced safely.
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This --verify-memory option is very system (Linux/Mac) dependent on how
the memory is allocated. This cannot be reproduce with same results.
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
I have not yet understood the meaning of --revalued-total, but as it
output something, it should be tested. So add it to "to be tested"
options list.
|
|\| | | | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Some documentation improvments about Ledger mode
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
[ci skip]
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
[ci skip]
|
| | |/ / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | | |
[ci skip]
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
[emacs] Fix bug 1060.
|
| | |/ / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Set as an option to kill (or not) the reconcile buffer after
ledger-reconcile-finish. The default is set to *not* kill the
buffer. This is justified as the facts that:
1. In old ledger mode (the one from Ledger 2.6), the default is to *not*
kill the buffer. Also for the ones who will migrate from 2.6 to 3 when
package will be available in their linux distribution, this will be the
path of least surprise.
2. The current documentation does state that the buffer is to be killed
with 'q' after 'C-c C-c'.
This has been made configurable, as killing buffer may already be part
of the workflow of some persons.
[ci skip]
|
| |\ \ \ \ \ \ \
| | |/ / / / / /
| |/| | | | | | |
Fix Bug 1108. Thanks.
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
[ci skip]
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The old way of working was keeping spaces before and after the
account. Now the space before is associated to the "status" and
"separator" is enlarged to not be maxed to 2 chars
[ci skip]
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Fix clang compile error (FreeBSD 10).
|
| |/ / / / / / |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Fix baseline test for --no-pager.
|
| |/ / / / / / |
|
|\| | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Conflicts:
lisp/ledger-reconcile.el
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Documentation improvements
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| | |/ / / / / /
| |/| | | | | | |
Fix Auto match
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
See http://en.cppreference.com/w/cpp/algorithm/max_element
and http://www.cplusplus.com/reference/algorithm/max_element/
The sorting for max requires < (and not >).
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Improve baseline tests
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
As per comment in Pull Request #382
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
As per commit f59abd4c765b08cbd5f18ec851b1d78a766a1c93
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
As per commit d5e1308d07e9a7d9da33aed6f7f617b2209cba40
|
| | | | | | | | | |
|
| |\ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Fix indentation and position of Fedora test.
[ci skip]
|
| | |/ / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
The blame for this section was a bit of a cluster, but, as someone who's not
using Fedora, this makes the most logical sense. (Fedora is a version of RH,
right?)
|
| |\ \ \ \ \ \ \ \
| | |/ / / / / / /
| |/| | | | | | | |
Fix alignment of cleared-format with 4 spaces as separator.
|
| |/ / / / / / / |
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Fix UUID of --rich-data test.
|
| | |/ / / / / / |
|