On Sun, Dec 4, 2016 at 12:29 AM, Stefano Zacchiroli wrote:
> On Sat, Dec 03, 2016 at 09:21:35AM -1000, Martin Blais wrote:
> > On Sat, Dec 3, 2016 at 1:48 AM, Stefano Zacchiroli
> wrote:
> > >
> > > It would be useful at some point if you could document best
> > > practices or other expectations
On Sat, Dec 03, 2016 at 09:21:35AM -1000, Martin Blais wrote:
> On Sat, Dec 3, 2016 at 1:48 AM, Stefano Zacchiroli wrote:
> >
> > It would be useful at some point if you could document best
> > practices or other expectations on how 3rd party plugins should be
> > "bundled up". That would make it
> I would say at the very minimum, every function/method should be called at
> least once; that's a good baseline. If you have complicated logic, you should
> have tests that exercise each of the main different use cases.
> Beyond that, it doesn't have to be exhaustive.
> For example, if you look
On Sat, Dec 3, 2016 at 1:48 AM, Stefano Zacchiroli wrote:
> On Fri, Dec 02, 2016 at 11:28:18AM -1000, Martin Blais wrote:
> > > > - people just publish them independently (or keep them private)
> >
> > Best to start this way IMHO.
> > See http://furius.ca/beancount/doc/contrib
> > Publish it and
On Fri, Dec 02, 2016 at 11:28:18AM -1000, Martin Blais wrote:
> > > - people just publish them independently (or keep them private)
>
> Best to start this way IMHO.
> See http://furius.ca/beancount/doc/contrib
> Publish it and I'll add a link there.
*nod*
This is now at https://github.com/zacchi
On Fri, Dec 02, 2016 at 04:55:25PM -1000, Martin Blais wrote:
> I've created a mirror at https://github.com/beancount/beancount
> I'm using hg-git, which works well enough.
> I'll try to keep this in sync with the Mercurial repo.
> (It seems like I can basically just push from my Mercurial client t
I've created a mirror at https://github.com/beancount/beancount
I'm using hg-git, which works well enough.
I'll try to keep this in sync with the Mercurial repo.
(It seems like I can basically just push from my Mercurial client to the
github git repo and it converts on-the-fly.)
Cheers,
On Fri,
On Fri, Dec 2, 2016 at 12:06 AM, Stefano Zacchiroli wrote:
> On Fri, Dec 02, 2016 at 09:42:29AM +0100, Dominik Aumayr wrote:
> > We could create a separate repository under
> > https://github.com/beancount for plugins from the community.
>
> Speaking of which, how about setting up
> https://githu
On Thu, Dec 1, 2016 at 10:42 PM, Dominik Aumayr wrote:
> > - some sort of "beancount forge" emerges, possibly blessed by you, as
> > central place where non-mainline plugins get contributed, with some
> > sanity checking on namespace to avoid naming clashes
>
> We could create a separate reposi
On Fri, Dec 02, 2016 at 09:42:29AM +0100, Dominik Aumayr wrote:
> We could create a separate repository under
> https://github.com/beancount for plugins from the community.
Speaking of which, how about setting up
https://github.com/beancount/beancount as an always up-to-date git
mirror of the hg r
> - some sort of "beancount forge" emerges, possibly blessed by you, as
> central place where non-mainline plugins get contributed, with some
> sanity checking on namespace to avoid naming clashes
We could create a separate repository under https://github.com/beancount for
plugins from the comm
On Mon, Nov 21, 2016 at 06:31:00AM -0800, Simon Michael wrote:
> 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.
Thanks Sim
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
Dear Beancounters,
attached you can find a plugin proposal which I'm using for my personal
Beancount needs but might be useful for others. If there is interest,
I'll be happy to submit it via the BTS, possibly adapting it to be more
generic before doing so.
The plugin validates that the in-file o
14 matches
Mail list logo
