Beancount Updates 2015-02-01
68 views
Skip to first unread message
Martin Blais
Feb 2, 2015, 2:35:04 AM2/2/15
to bean...@googlegroups.com, ledger-cli
2015-02-01
- Implemented an "include" directive. The include directive does not parse the
files in order... rather, each parse run on an input file accumulates the
list of includes to be parsed and processed the includes after parsing the
file. Because we're order independent, this should work. Note however that
the options should be set in the root file.
This is documented here:
redst...@gmail.com
Feb 3, 2015, 12:09:59 AM2/3/15
to bean...@googlegroups.com, ledge...@googlegroups.com
Excellent, this makes things cleaner for me, thank you.
One question: previously, if I wrote to the beancount file that a bean-web process was already using, and if I hit refresh, bean-web noticed the update to the file and re-read. This still works now, but only on the including file, not on the included files. Is this a pain to fix, or relatively easy?
Martin Blais
Feb 3, 2015, 1:00:18 AM2/3/15
to redst...@gmail.com, bean...@googlegroups.com, ledger-cli
On Tue, Feb 3, 2015 at 12:09 AM, <redst...@gmail.com> wrote:
Excellent, this makes things cleaner for me, thank you.
Keep in mind I did all the development using unit tests, I haven't actually used it on my file yet, so it might still have rough edges.
One question: previously, if I wrote to the beancount file that a bean-web process was already using, and if I hit refresh, bean-web noticed the update to the file and re-read. This still works now, but only on the including file, not on the included files. Is this a pain to fix, or relatively easy?
Oops, hadn't thought about that one.
I guess I'll need to add this bit then:
And modify the web app so that it detects it for a set of files here:
--
You received this message because you are subscribed to the Google Groups "Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beancount+...@googlegroups.com.
To post to this group, send email to bean...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/d2782141-fb25-49d6-aa97-d5e6b52a0b58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
redst...@gmail.com
Dec 6, 2015, 10:13:58 PM12/6/15
to Beancount, redst...@gmail.com, ledge...@googlegroups.com
On Monday, February 2, 2015 at 10:00:18 PM UTC-8, Martin Blais wrote:
On Tue, Feb 3, 2015 at 12:09 AM, <redst...@gmail.com> wrote:One question: previously, if I wrote to the beancount file that a bean-web process was already using, and if I hit refresh, bean-web noticed the update to the file and re-read. This still works now, but only on the including file, not on the included files. Is this a pain to fix, or relatively easy?Oops, hadn't thought about that one.I guess I'll need to add this bit then:And modify the web app so that it detects it for a set of files here:
Done, and pull request created:
Unfortunately, BEANCOUNT_DISABLE_LOAD_CACHE must be set for this feature to work. Could you please see if there's a better way? Thanks!
Martin Blais
Dec 8, 2015, 9:21:33 AM12/8/15
to Beancount, redst...@gmail.com, ledger-cli
This issue has been addressed:
Both the load cache and bean-web should now correctly watch for changes in the entire set of included files.
--
You received this message because you are subscribed to the Google Groups "Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beancount+...@googlegroups.com.
To post to this group, send email to bean...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/d809ad38-6852-4123-88f1-e23332c2a330%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages