| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Also, support matching provided hashes against a prefixed of the generated
hash.
|
| |
|
| |
|
|
|
|
|
| |
At the moment only "sha512" or "SHA512" is accepted, but this could extend to
more algorithms in the future.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The following details of a posting contribute to its hash:
fullname of account
string representation of amount
Each posting hashes contributes to the transaction hash, which is compromised
of:
previous transaction’s hash (as encountered in parsing order)
actual date
optional auxiliary date
optional code
payee
hashes of all postings
Note that this means that changes in the “code” or any of the comments
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Multiprecision rational created from a double value may have large power
of 2 denominator since fractional decimal numbers can not be represented
as binary floating point numbers. It leads to failed assertion when
result is compared to a value converted directly from strings.
Use integer multiprecision arithmetics to round numbers to ensure
proper denominator. Inspired by python gmpy2 package
<https://github.com/aleaxit/gmpy/blob/3e4564ae9d/src/gmpy2_mpq_misc.c#L315>
The change makes `roundto` symmetric for positive/negative arguments.
Halves are rounded to nearest even. Rounded away from zero are discussed
in #1663 and it may be achieved with minimal modification.
- See #2329
- Closes #1983
|
|\ |
|
|/
|
|
|
|
|
|
|
| |
The script has a syntax error, caused by commit 815305b9: in escape_string()
function the first argument to re.sub() was probably changed unintentionally.
This reverts this one line. To test, I used acprep to build the binary locally,
which succeeded. More testing might be needed, I don't have enough context to
do that.
|
|
|
|
| |
[ci skip]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the account name is longer than the --account-width (default 36),
the amounts stop aligning:
2023/01/01 Transaction with long account names
Assets:Very:Long:Account:Name:That:Will:Push:The:Amount -10 ABC
Assets:Another:Long:Account:Name:That:Will:Push:The:Amount -10 ABC
Expenses:Short 20 ABC
One can set a larger --account-width, but that is not a great solution
for cases where you have only a few accounts with problematically long
names. Instead, keep the current account width wherever possible, but
when an account name is longer than the account width, account for that
and still align the values:
2023/01/01 Transaction with short account names
Assets:Short -10 ABC
Assets:Short -10 ABC
Expenses:Short 20 ABC
2023/01/01 Transaction with long account names
Assets:Very:Long:Account:Name:That:Will:Push:The:Amount -10 ABC
Assets:Another:Long:Account:Name:That:Will:Push:The:Amount -10 ABC
Expenses:Short 20 ABC
This is similar to hledger's behavior.
|
| |
|
| |
|
|
|
|
| |
Fixes #2324
|
| |
|
|
|
|
|
|
| |
as "the global configuration variable Py_UnbufferedStdioFlag was
deprecated in Python 3.12 and using PyConfig.buffered_stdio is
recommended instead." — https://peps.python.org/pep-0741/
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Part of the expr_t::compile() process is to store the current scope, but
In post_t::add_to_value that scope is temporary and on the stack.
Restore the original context after that process is complete.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add failing test for use case
TBH I don't know what I'm doing here, but this seems to fail for the
right reasons enough to reflect the parser bug here.
* Append to the ident on a closing brace ')'
When parsing the automated rule, a scanner reads the line left-to-right
char-by-char. The default behaviour is to append the char under the
cursor to some `ident` string. When the cursor is on a ')', it skips the
default handling and switches into some special handling: it tries to
test the string it's reading if it's one of the keywords it knows, to
select which type of token just got scanned. If what was scanned is not
a known token, it defaults to `token_t::TERM` and returns a new token
with the currently accumulated `ident` as a `token_t::TERM`. Issue is,
since it skipped the appending to do some custom handling, the
`token_t::TERM` will always be without its closing brace. The scanner
needs to append the character under the cursor if it's falling through
to default processing.
* fix test case
- ensure proper spacing for the posting to have an amount
- ensure the posting balances against an account
- the meaning of the number after `->` is the exit code
* undo wrong approach
* consume_next if unbalanced_braces
* how this can be extended
|
|\
| |
| |
| |
| | |
ledger/dependabot/github_actions/cachix/install-nix-action-27
chore(deps): bump cachix/install-nix-action from 26 to 27
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [cachix/install-nix-action](https://github.com/cachix/install-nix-action) from 26 to 27.
- [Release notes](https://github.com/cachix/install-nix-action/releases)
- [Commits](https://github.com/cachix/install-nix-action/compare/v26...V27)
---
updated-dependencies:
- dependency-name: cachix/install-nix-action
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|\
| |
| | |
Fix build with Boost 1.85.0
|
|/
|
|
| |
Signed-off-by: Michael Cho <michael@michaelcho.dev>
|
|\
| |
| |
| |
| | |
ledger/dependabot/github_actions/cachix/install-nix-action-26
chore(deps): bump cachix/install-nix-action from 25 to 26
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [cachix/install-nix-action](https://github.com/cachix/install-nix-action) from 25 to 26.
- [Release notes](https://github.com/cachix/install-nix-action/releases)
- [Commits](https://github.com/cachix/install-nix-action/compare/v25...v26)
---
updated-dependencies:
- dependency-name: cachix/install-nix-action
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
| |
|
| |
|
|\
| |
| |
| |
| | |
ledger/dependabot/github_actions/cachix/install-nix-action-25
chore(deps): bump cachix/install-nix-action from 24 to 25
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [cachix/install-nix-action](https://github.com/cachix/install-nix-action) from 24 to 25.
- [Release notes](https://github.com/cachix/install-nix-action/releases)
- [Commits](https://github.com/cachix/install-nix-action/compare/v24...v25)
---
updated-dependencies:
- dependency-name: cachix/install-nix-action
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|\
| |
| | |
Update acprep
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
being deprecated as of C++11
|
|\ \
| | |
| | | |
utfcpp: Update to 4.0.4
|
| | | |
|
|\ \ \
| | | |
| | | | |
test: Accept test names as arguments
|
| | | | |
|
|/ / / |
|
|/ / |
|
|\ \
| |/
|/| |
Minor documentation update - on posting comments and fixed some examples
|
| |
| |
| | |
Co-authored-by: Alexis Hildebrandt <afh@surryhill.net>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Added to "Transactions and Comments" section 4.7.1 to indicate that
posting comments *must* be preceded by at least two spaces.
I also applied this rule consistently to the entire documentation, which
only required changes in 4 locations.
I don't think the `ledger` binary cares about spaces in front of posting
comments. I never noticed this until I tried using `ledger-mode`'s
`ledger-post-edit-amount`, which was causing issues with comments
that don't have the proper spacing.
|
|\ \
| | |
| | | |
Add support for Ubuntu 22.04 Jammy in ./acprep
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Running `./acprep dependencies` in Ubuntu 22.04 Jammy while
building ledger from source returns:
acprep: INFO: Invoking primary phase: dependencies
acprep: INFO: Executing phase: dependencies
acprep: INFO: Installing Ledger's build dependencies ...
acprep: INFO: Looks like you are using APT on Ubuntu jammy
acprep: INFO: I do not recognize your version of Ubuntu!
This error was also present when installing on Ubuntu 20.04
Focal. The solution for Focal is the same for Jammy, which is to
add `ubuntu-jammy` to `BoostInfo` and `jammy` as another `release`.
|
|\ \ \
| | | |
| | | | |
tests: Modernize test scripts
|