| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Instead of using a "magic" value (12), use the proper variable to set
the width.
|
| |
|
|
|
|
|
| |
Should fix problem with garbage being read from this field causing some
test failures on my machine.
|
| |
|
|
|
|
| |
file
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Fix bug where .total used in value exprs breaks totals
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Re-initialize (to VOID) totals for the account and its ancestors on adding
postings. Otherwise the cache intended for use by recursive calls of C++
function total() in computing family (i.e. account hierarchy) totals is
incorrectly retained from one top-level call to the next, causing
inconsistent and broken behaviour.
* Re-initialize (to false) calculated and gathered. Otherwise we won't
e.g. recalculate stale totals for ancestor accounts (e.g. won't recalculate
Assets:Savings total if Assets:Savings changes via a posting).
Although the value expression total function is used by ledger itself in
computing totals, this bug would only appear on use of .total in user-supplied
value expressions computed *during parsing* of ledger files, rather than after
parsing (I believe ledger only ever calls it for internal purposes after
parsing is complete).
It is possible this bug also affected other functions than total (perhaps even
in circumstances other than analagous to that described in the preceding
paragraph). I have not checked that.
|
|\ \
| | |
| | | |
Fix Bug 1182: Error message for parse failure after '='
|
| | | |
|
|\ \ \
| | | |
| | | | |
Fix MSVC build
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
Remove compiler warning about missing braces
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Remove the following warning from gcc 5.4.0: "[...]/src/output.cc:335:6:
warning: suggest explicit braces to avoid ambiguous ‘else’
[-Wparentheses]".
Instead of adding braces around the whole function body, return early if
item.metadata is 0.
|
|/ / |
|
| |
| |
| |
| | |
[ci skip]
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This was reported as Bug #1109
|
| |
|
|\
| |
| | |
Fix Windows strptime
|
| |
| |
| |
| | |
This fixes the datetime-related tests in testAddition and testSubtraction in the LedgerMathTests
|
|\ \
| | |
| | | |
Use boost parent_path() method instead of manual computation
|
| |/
| |
| |
| | |
This fixes error-in-include.test, dir-apply.test, 6188B0EC.test, and 89233B6D.test when running under msys2 on Windows. The manual computation is incorrect when there are both forward slash and backward slash characters in the path.
|
|/ |
|
|\
| |
| | |
Fix compilation error with boost 1.61
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
| |
* Appveyor is a continuous integration platform for Windows that is free for open source projects. See latest test build here: https://ci.appveyor.com/project/Evan/ledger/build/artifacts
* Changed WIN32 to _WIN32 because this article http://nadeausoftware.com/articles/2012/01/c_c_tip_how_use_compiler_predefined_macros_detect_operating_system claims that it is defined by the greatest number of compilers.
* Modified HAVE_ISATTY and other system defines so that system.hh compiles when cmake fails to find the relevant function.
* Add missing include in test/unit/t_value.cc
Almost all tests fail when you run them on msys32. I will address that in a future PR.
|
|
|
|
| |
This reverts commit 11590e134eafa768ccc4a171cc7fb216e906095f.
|
| |
|
|\
| |
| | |
Use interval start date (period from/since) to initialize first period.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
transaction date
Bug 1159
Use interval start date (period from/since) to initialize first period.
This allows the offset of a period start to be specified
-p 'every 12 months from 2000-04-01'
will have periods
yyyy-04-01 to yyyy-03-31
....
If no from/since is specified for the period the first transaction date reported is used to initialize the period as before.
added test case regress/1159.test
|
|/
|
|
|
|
|
|
| |
weeks - calculate start date for finding period using remainer 400/periodlength to reduce number of iterations (perhaps this ought to follow the same conventio as years months and quarters)
add sample period command tests
add add day period tests for forecasts and budgets
add week period tests for forecasts and budgets - these do not change
|
|
|
|
| |
Fixes bug #981
|
|
|
|
|
| |
When converting a ledger.Value to unicode the Python API added
double quotes around it.
|
| |
|
|
|
|
| |
when using boost version 1.60.0.
|
|
|
|
| |
[ci skip]
|
|
|
| |
when using version 1.59.0
|
|\
| |
| | |
Add regression test file for bug #1057
|