| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
| | | |
| | | |
| | | | |
macOS seems to be the current name for Mac OS X.
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | | |
| | | | | |
explain round brackets in section 3.8 on multiple funds
|
| |/ / /
| | | |
| | | | |
Section "Working with multiple funds and accounts" introduces square brackets and explains them but does not explain round brackets in the following example. This commit adds the explanation what the round brackets do.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | | |
| | | | | |
Improve bash completion
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We now complete option shorthands
[ci skip]
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes #1676
|
| |/ / / |
|
| |\ \ \
| | | | |
| | | | | |
Add notes to 5.7.1.1 Payee metadata tag doc
|
| | | | | |
|
| |/ / / |
|
| | | | |
|
| | | | |
|
| |\ \ \ |
|
| | |\ \ \
| | | | | |
| | | | | | |
inhibit read only when inserting in *Ledger Error*
|
| | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When ledger-exec-handle-error is called a second time, it try to insert
the error in a buffer that is already read-only. inhibit-read-only
permit the insertion.
|
| | |\ \ \
| | | | | |
| | | | | | |
Ensure that parse errors produce useful RuntimeErrors for Python code.
|
| | | | | | |
|
| | | | | | |
|
| | |\ \ \ \
| | | |/ / /
| | |/| | | |
Require correct feature
|
| | |/ / /
| | | | |
| | | | |
| | | | |
| | | | | |
In `ledger-matching.el' require `ledger-report' instead of `ldg-report'.
That library was renamed like all the others.
|
| |\ \ \ \
| | | | | |
| | | | | | |
Improve fix of issue #1187
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |/ / / / |
|
| |\ \ \ \
| | | | | |
| | | | | | |
Unbreak build against Boost 1.68
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In file included from src/main.cc:34:
In file included from src/global.h:41:
In file included from src/option.h:45:
In file included from src/scope.h:45:
In file included from src/op.h:45:
In file included from src/expr.h:45:
In file included from src/exprbase.h:57:
src/utils.h:47:10: fatal error: 'boost/uuid/sha1.hpp' file not found
#include <boost/uuid/sha1.hpp>
^
|
| | | | |
| | | | |
| | | | |
| | | | | |
The transaction state comes before (not after) the code.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes #1192
|
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes #1658
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
file paths"
This reverts commit 3364850cc7cf73fc67af1ea6cd9a65a32e336623.
Fixes #559
|
| |\ \ \
| | | | |
| | | | | |
Fix garbled dates when using --date-format
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Capture the `std::string` value from options in a local variable that
lives as long as the `c_str()` taken from it to ensure it does not get
freed prematurely.
Fixes: #546
|
| |\ \ \
| | | | |
| | | | | |
Remove TOK_A_YEAR token
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This fixes #1626.
The tokenizer eagerly classifies 4-digit integers as TOK_A_YEAR
tokens. In some contexts such as "every 1000 years", this causes
errors.
I think the tokenizer does not have enough information available to
distinguish between integers and years.
After this patch, the tokenizer will always classify integers as
TOK_INT tokens. The "has 4 digits" heuristic to determine if an
integer is a year is moved to the place where it's actually
needed (and it can be slightly more generic there, too).
|
| |\ \ \
| | | | |
| | | | | |
Documents commodity directive's alias sub-directive
|
| |/ / / |
|
| |\ \ \
| | | | |
| | | | | |
Make automated transactions work with assertions
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This fixes issue #1127. In my understanding, PR #552 was meant to fix
this, but was incomplete.
Without this patch, automated transactions are invisible to
assertions.
This patch fixes this by adding a flag to the account to tell it that
there is a new posting, analogous to the behavior of finalize().
I dug up issue #1127 too late to find that this is the same solution
proposed by @tbm. Although I wrote this independently, credit goes to
Martin Michlmayr (@tbm).
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The old "fixed" and "endfixed" are no longer used (and afaict don't
work). You have to use "apply fixed" and "end apply" instead.
Fixes issue #789
Signed-off-by: Martin Michlmayr <tbm@cyrius.com>
|
| | | | |
|
| |\ \ \
| | | | |
| | | | | |
Add documentation on how to sort in reverse order
|