Issue #147: plugins declared in include-d files are ignored (blais/beancount)
12 views
Skip to first unread message
Stefano Zacchiroli
Nov 11, 2016, 10:20:34 AM11/11/16
to bean...@googlegroups.com
New issue 147: plugins declared in include-d files are ignored
https://bitbucket.org/blais/beancount/issues/147/plugins-declared-in-include-d-files-are
Stefano Zacchiroli:
I'd like to keep my "main" ledger clean, with a single "include header.beancount", which in turn includes beancount files with various roles (account openings, commodities declarations, etc).
Most notably I'd like to have a plugins.beancount file that lists all plugins to be loaded, and that doesn't seem to work.
plugin declarations are effective if I put them in the top-level beancount file, but are completely ignored (i.e., the plugins are not executed) if I move them to (recursively) included files. This is, at least, according to bean-check which I'm using to test this.
It would be nice if one could put plugin declarations in any (recursively) included beancount files, without any semantic change in beancount behavior.
https://bitbucket.org/blais/beancount/issues/147/plugins-declared-in-include-d-files-are
Stefano Zacchiroli:
I'd like to keep my "main" ledger clean, with a single "include header.beancount", which in turn includes beancount files with various roles (account openings, commodities declarations, etc).
Most notably I'd like to have a plugins.beancount file that lists all plugins to be loaded, and that doesn't seem to work.
plugin declarations are effective if I put them in the top-level beancount file, but are completely ignored (i.e., the plugins are not executed) if I move them to (recursively) included files. This is, at least, according to bean-check which I'm using to test this.
It would be nice if one could put plugin declarations in any (recursively) included beancount files, without any semantic change in beancount behavior.
Reply all
Reply to author
Forward
0 new messages