| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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).
|
| | |
|
|\ \
| | |
| | | |
Add support for --prepend-format in accounts command
|
| | |
| | |
| | |
| | |
| | | |
Add support for the `--prepend-format` and `--prepend-width` options in
the `accounts` command.
|
|\ \ \
| | | |
| | | | |
Fix handling of edge cases in trim function
|
| |/ /
| | |
| | |
| | | |
Fixes #520
|
|/ /
| |
| |
| | |
[ci skip]
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`changed_value_posts::create_accounts()` reuses the `<Revalued>` account
from `display_filter`, but when clearing `changed_value_posts`
`create_accounts()` would be called before the account had been
recreated by `display_filter_posts`. This results in a segfault when
using the --group-by option.
I'm not sure if `display_filter_posts` has the same problem but I
reordered the calls there too for good measure.
|
|\ \
| | |
| | | |
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 test
|
|\ \ \
| | | |
| | | | |
Add regress test for bugs 550 and 584
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Add regress test for bug 1055
|
| |/ / / |
|
|/ / / |
|
|/ /
| |
| |
| | |
[ci skip]
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
To verify that no ANSI color codes are printed when the --force-color
option is not set.
|
| | |
|
| |
| |
| |
| | |
This was reported as Bug #1109
|
| | |
|
|\ \
| | |
| | | |
Fix regress test 383 on Windows
|
| | |
| | |
| | |
| | | |
%g is not available in Windows strftime. See documentation at https://msdn.microsoft.com/en-us/library/fe06s4ak.aspx
|
|\ \ \
| |/ /
|/| | |
Fix build under Cygwin
|
| | | |
|
|/ /
| |
| |
| |
| |
| | |
With this change, 97% of the tests pass. See the build on appveyor for more info: https://ci.appveyor.com/project/Evan/ledger/build/build-49
I'll follow up with another PR to fix some of the remaining broken tests
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* 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.
|
| | |
|
|\ \
| | |
| | | |
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
|
| |
| |
| |
| |
| | |
I'm sure I used $FILE for the final version but I must have committed
an old version.
|
| |
| |
| |
| | |
Fixes bug #981
|
|/
|
|
|
| |
When converting a ledger.Value to unicode the Python API added
double quotes around it.
|
|
|
|
| |
[ci skip]
|
| |
|
| |
|
|
|
|
|
|
| |
warning: equality comparison result unused [-Wunused-comparison]
BOOST_CHECK_THROW(v8 == v10, value_error);
~~~^~~~~~
|
|
|
|
| |
For consistency as this is a directive.
|
|
|
|
| |
due to timezone settings.
|
|
|
|
| |
so that the tests run with a consistent environment.
|
|\
| |
| | |
Add regression test file for bug #1057
|
| |
| |
| |
| |
| | |
-(("/home/travis/build/ledger/ledger/test/regress/1057.test" 1 (21308 34912 0) nil "www.amazon.fr"
+(("/home/travis/build/ledger/ledger/test/regress/1057.test" 1 (21308 42112 0) nil "www.amazon.fr"
|