| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fixes #417.
|
| |
|
|
|
|
| |
This reverts commit 48aec0f093ff6494a3e4f7cd5166cb4a27c16814.
|
|
|
|
| |
This reverts commit 68c9d649caa2c7c7f222613efe86576c379a5a7a.
|
| |
|
|
|
|
| |
Instead we use boost::none, which has been documented since boost 1.34.0.
|
| |
|
| |
|
| |
|
|\
| |
| | |
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 >).
|
|/ |
|
|
|
|
| |
and all boost serialisation related code.
|
|
|
|
| |
since it is the same as --help.
|
|
|
|
|
|
| |
std::isspace(*e) returns false for the end of c-string null-byte.
Bugzilla: 1106
|
|
|
|
| |
Bump version to 3.1.1-alpha.1
|
| |
|
| |
|
|
|
|
|
|
| |
Bugfix for #1102
Signed-off-by: Alexis Hildebrandt <afh@surryhill.net>
|
|
|
|
|
|
|
| |
to check whether all available ledger options documented
and are being tested.
Signed-off-by: Alexis Hildebrandt <afh@surryhill.net>
|
| |
|
| |
|
|
|
|
|
| |
when year was specified with literal Y or year directive, but not
when using apply year.
|
|
|
|
|
|
|
| |
A literal Y directive or ‘year’ directive with an empty or invalid
argument, e.g. ‘2o14’ (that is a small letter ‘oh’ instead of a zero)
would fail with the following rather unhelpful error message:
Error: bad lexical cast: source type value could not be interpreted as target
|
|
|
|
| |
Only Y2014 or apply year 2014 would actually set the year for the
following transactions; year 2014 would silently do nothing.
|
| |
|
|
|
|
|
|
| |
The following script makes it a no-brainer:
% NEXT_YEAR=2015; ag -l 'Copyright.*Wiegley' \
| xargs sed -i '' -e "s/\(Copyright.*\)-20[0-9]\{2\}/\1-${NEXT_YEAR}/"
|
|
|
|
| |
[ci skip]
|
|
|
|
|
| |
uint8_t is typedef'd to char, thus boost::lexical_cast treats it
as such instead of a number.
|
|
|
|
|
|
|
| |
ledger -f /dev/null reg -M test causes a segmentation fault,
see bug 730 and duplicates 1080 and 1084 for details.
Kudos to Ikke for helping with debugging.
|
|
|
| |
This fixes parsing of transactions with single-character payees and comments.
|
|
|
|
| |
cargo-cut'n'paste from py_amount.cc
|
|
|
|
|
| |
Discussion:
https://groups.google.com/d/msg/ledger-cli/kq9sKoRX9vw/fmyhvPslzokJ
|
|
|
|
|
|
|
|
|
|
|
| |
If set, the COLUMNS environment variable will take precedence over terminal
width. However, please note that COLUMNS is usually *not* exported by shells to
child processes, so in most cases COLUMNS will be undefined for ledger---hence
the motivation for this change.
Terminal width is queried using ioctl() on stdin. For the sake of portability
the querying is done only on platform where ioctl() is detected as supported at
compile-time.
|
|
|
|
|
|
|
|
| |
Dates specified via --begin and --end are converted to a value expression
using an ISO 8601 (yyyy-mm-dd) date, but this date was not recognized by
ledger.
Bug fix for #1072
|
|
|
|
| |
Bug fix for #1074, a regression introduced by the fix for bug #375
|
| |
|
| |
|
| |
|
|
|
|
| |
This reverts commit df9ae3ab9b37fde803f26c6bc4eaadfd67fc1d07.
|
|
|
|
| |
This reverts commit 38557ee63273dcdef22b136c5f424802c7ff6e03.
|
| |
|
| |
|
|
|
|
| |
See emails in group from John Rakestraw circa November 2011
|
|
|
|
| |
Patch from John Wiegley
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change the definition of cost: in the past, if you bought 1 AAA for
$10 and then sold it for $12, ledger would take $12 as the cost. With
the patch, the original cost of $10 is preserved ss the cost basis.
In my opinion, this brings ledger in line with accounting expectations.
This change fixes bugs #712 and #713.
Bug #712 is about Equity:Capital Gains and Equity:Capital Loss
entries ledger automatically generates that are in my opinion
incorrect.
Bug #713 is about strange behaviour with -B after a capital gain or
loss is made.
Patch from John Wiegley.
|
|
|
|
|
| |
Debugging categories follow the filename, which in this case is singular
(rather than plural) "account" and "amount".
|
|
|
|
| |
posting, it always has a priority over entire transaction status.
|
| |
|
|
|
|
|
|
|
|
| |
When a cost was specified without a whitespace after the @ symbol,
as in @$5.01, this was incorrectly parsed as 5.01 (losing the
commodity) rather than $5.01.
Bug fix for #1050
|