You're right that scheme code logging is useful.
The scheme way is to use pk, such as
(pk "qif acct map is" qif-acct-map)
But often you'll find that gnc objects are opaque; you can use (gnc:pk "qif
acct map is" qif-acct-map) instead.
You can combine multiple objects with pk or gnc:pk (gnc:pk
Well, with no hint of what the problem is, even smaller
test sets won't necessarily find anything, so it could be
a lot of work for no benefit. For example, I could export
each account separately (although there are about 80 of them
so that's a lot of work), and each account could load
okay
On Tue, Feb 18, 2020 at 4:07 PM crazylyle wrote:
> So you are suggesting reducing the size of our QIF files to a small
> debuggable size.
>
> My QIF file is 653,808 lines long. About 2^20. So just using a binary
> search would
> take at least 20 trials to find the first line that it fails on.
So you are suggesting reducing the size of our QIF files to a small
debuggable size.
My QIF file is 653,808 lines long. About 2^20. So just using a binary
search would
take at least 20 trials to find the first line that it fails on. Not
exactly something that
seems practical. And that's just
Forward from devel
-- Forwarded message -
From: Geert Janssens
Date: Tue, 18 Feb 2020, 3:48 pm
Subject: Re: [GNC-dev] Fwd: [GNC] Failed - import of QIF files from Quicken
To:
Cc: Christopher Lam
Hi Tom,
We don't need your complete financial history, just the bit
