- `+beancount/clone-transaction` now completes for all transactions
across this and any included files (depending on the value of
`+beancount-files`).
- Handles an edge case where `+beancount/clone-this-transaction` would
try and fail to clone a transaction at point where there wasn't any.
Enhances completion for beancount-mode in the following ways:
1. Adds completion for:
- Event directives and values,
- The payee field in transactions,
- Currencies and commodities,
2. Fixes completion for #tag and ^links not working at the end of a
transaction's heading.
3. Completion now scans not only the current file, but any included
files (recursively) for candidates if `+beancount-files' is set to
`auto`. It can otherwise be set to a list of static files or set to
`nil` (reverts to only scanning the current buffer). This applies not
only to completion-at-point functions, but also interactive commands
like `beancount-insert-account'.
This is all very rudimentary and needs polish!
Adds support for meta lines that only the flymake linter will see.
These are lines prefixed by any number of semicolons followed by a hash
then space. E.g.
;# include "../config.beancount"
;# 2025-01-01 pad Assets:Bank Equity:Opening-Balances
This is useful for silencing the linter in multi-file beancount projects
rather than suffer the usual deluge of multiple-include errors and
redundancies.
magit/transient@HEAD -> magit/transient@25b994a565
Seems to be a source of many issues the past month or so. About time we
pin it by stable release.
Fix: #8394
Beancount tools and Fava recognize relative paths in include and
document directives, and documents options. However, flymake-bean pipes
the buffer's contents to bean-check via /dev/stdin, so paths are
resolved relative to /dev instead of the location of the containing
beancount file, resulting in file errors. This commit expands those
relatives paths before sending the buffer's contents to bean-check to
resolve these false positives.
Not a complete fix, because +vc-gutter-update-h isn't aggressive or
responsive enough to changes in VC in buffers that haven't changed, but
I'll address that later.
c-ts-mode and c++-ts-mode weren't being remapped to from c-mode/c++-mode
because of extra noise in `major-mode-remap-defaults`. I wish these
packages would leave these variables alone and leave it to the user to
configure; they're often inconsistent and overbearing.
This is due to other dedicated/side popups and/or windows causing the
undo-tree visualizer buffer to open in difficult-to-delete windows. This
should be reported and addressed upstream, though.
Fix: #8198
BREAKING CHANGE: This rewrites the :tools tree-sitter module to use
treesit instead of tree-sitter.el. Users will need to adapt to treesit
and remove any tree-sitter-specific config in their dotfiles.
Ref: #7623
Ref: #7742
Ref: #8197
In cases where user have changed `vc-follow-symlinks`,
causing *Messages* spam and unexpected prompting, OR where revert-buffer
hooks and handlers are prematurely triggered for file buffers that
haven't been changed.
Fix: #8392
I'm only trying to override the RET key that evil-org binds, but also
binding these to [return] interferes with "RET" keybinds in various
places, like transient bindings on RET (e.g. gptel).
Conform keybinds to MacOS conventions for font resizing commands.
Also:
- Moves numbered workspace keybinds out of +evil-bindings.el so non-evil
users can enjoy them.
- Rebinds s-0 from +workspace/switch-to-final to doom/reset-font-size.
Fix: #8379
Amend: b70d137f1a
