On 11/21/16 1:50 AM, Stefano Zacchiroli wrote:
But *if* you adopt the style of linear, date-ordered Beancount file(s),
then this plugin might help you in detecting errors. The typical error
that I'm successful avoiding with this plugin is copy-pasting an old
transaction as a more recent one, but forgetting to bump its date.
I haven't done so because I don't personally need it, but it should be
trivial to make the plugin configurable to, e.g., allow reverse ordering
and/or ensure that transactions are strictly ordered according to
metadata other than date. I'll be happy to support this if there is
interest from others.
As this is my first Beancount plugin, I also welcome comments on the
code and approach.
Hi Stefano,
just on the general idea: I think it's a good one! At least in my
workflow, it's surprisingly easy to make this mistake and to lose time
tracking it down during reconciliation. I'm going to start doing a
similar check.
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beancount/o0v0es%24qi5%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.
