On Sun, Jul 23, 2023 at 3:19 AM Daniele Nicolodi wrote:
> On 23/07/23 03:58, Eric Altendorf wrote:
> ...
> > I'm not sure how one is supposed to run multiple importers at once, the
> > doc kind of only describes running one.
>
> This is a design document, not user documentation. What has been
>
On 23/07/23 12:19, Daniele Nicolodi wrote:
It should, but I just found that indeed I overlooked some divergence in
the code paths between the time the intra-importer deduplication patches
were written and the time I merged them. As a result, the intra-importer
deduplication is not run. This is
On 23/07/23 03:58, Eric Altendorf wrote:
That's great! I have pulled the latest code, and it doesn't seem to be
deduplicating the expected items. Let me check my assumptions:
I'm not sure how one is supposed to run multiple importers at once, the
doc kind of only describes running one.
On Sat, Jul 22, 2023 at 3:34 AM Daniele Nicolodi wrote:
> On 21/07/23 23:06, Eric Altendorf wrote:
> > I'm trying to figure out whether I can use the Beangulp import driver
> > with hooks, or if I need to write my own driver to call my importers and
> > do postprocessing. As you may recall, my
On 22/07/23 12:34, Daniele Nicolodi wrote:
On 21/07/23 23:06, Eric Altendorf wrote:
I'm trying to figure out whether I can use the Beangulp import driver
with hooks, or if I need to write my own driver to call my importers and
do postprocessing. As you may recall, my workflow is atypical, as I
On 21/07/23 23:06, Eric Altendorf wrote:
I'm trying to figure out whether I can use the Beangulp import driver
with hooks, or if I need to write my own driver to call my importers and
do postprocessing. As you may recall, my workflow is atypical, as I
have no curated Beancount ledger file; my
