We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
t
Consider the following transaction:
; 2025/01/06 * Cinema Expenses:Cinema €18.00 Cash
With point after the initial comment, pressing space gives
Company: backend company-capf error "Not on a posting line" with args (candidates ; )
This is when using:
(add-hook 'ledger-mode-hook (lambda () (setq-local tab-always-indent 'complete) (setq-local completion-cycle-threshold t) (setq-local ledger-complete-in-steps t)))
The problem comes from (setq-local ledger-complete-in-steps t), which activates the use of ledger-complete-account-next-steps where we have:
(setq-local ledger-complete-in-steps t)
ledger-complete-account-next-steps
(unless (eq 'posting (ledger-thing-at-point)) (error "Not on a posting line"))
My guess is that using company-mode together with ledger-complete-in-steps set to t is not intended, but there are valid use cases.
company-mode
ledger-complete-in-steps
If I simply remove the (error "Not on a posting line") things seem to work fine (the tests pass).
(error "Not on a posting line")
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Consider the following transaction:
With point after the initial comment, pressing space gives
This is when using:
The problem comes from
(setq-local ledger-complete-in-steps t)
, which activates the use ofledger-complete-account-next-steps
where we have:My guess is that using
company-mode
together withledger-complete-in-steps
set tot
is not intended, but there are valid use cases.If I simply remove the
(error "Not on a posting line")
things seem to work fine (the tests pass).The text was updated successfully, but these errors were encountered: