If what I asked cannot be done i will try to produce a file with the errorsome
other way
I would suggest to take these emails offline. I think they confuse the user
community
I will be in touch
Thanks
On Feb 18, 2020 5:34 PM, "Frank H. Ellenberger"
wrote:
Am 18.02.20 um 22:52 schrieb Chr
Where to look does depend on the source of your flatpak unfortunately.
The link John points to is the one used for the gnucash nightly flatpak builds
which you can
download from https://code.gnucash.org/builds/flatpak/
If however you used the flatpak provided by flathub, the link would be
https
They should not be taken off-line, they should be taken to gnucash-devel.
I have purposely left gnucash-user in cc in this mail to inform everybody, but
please on future
replies remove gnucash-user from the recipient list and only post to
gnucash-devel.
Regards,
Geert
Op woensdag 19 februari
Op dinsdag 18 februari 2020 23:04:59 CET schreef crazylyle:
> 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 f
Hello Souksakhone,
Am 11.02.20 um 19:27 schrieb Souksakhone Phomphakdy:
> Hello Frank,
>
> Thank you for your prompt reply. I really appreciated it. I had used many Lao
> keyboards type Lao in GnuCash but I was not successful. See attached file for
> how it looks. I can type Lao in other progra
Moved to devel because this is developer stuff. It's difficult because the
programming was done 20 years ago when toolkits were much more primitive.
You have two options to log.
in C, add PWARN ("retval is %s", retval? "True" : "False"); in
assistant-qif-import.c:3050
in guile, add (gnc:pk "object
The version info can also be obtained via:
➜ ~ flatpak run --command=sh org.gnucash.GnuCash
[📦 org.gnucash.GnuCash ~]$ aqbanking-cli versions
Versions:
AqBanking-CLI: 6.1.0
Gwenhywfar : 5.2.0.0
AqBanking: 6.1.0.0
> On Feb 19, 2020, at 1:06 AM, Geert Janssens
> wrote:
>
> Where to loo
Right, and even in one single command like this:
~ flatpak run --command=aqbanking-cli org.gnucash.GnuCash versions
Regards,
Geert
Op woensdag 19 februari 2020 16:53:40 CET schreef chris graves:
> The version info can also be obtained via:
> ➜ ~ flatpak run --command=sh org.gnucash.GnuCash
>
Hi,
Adrien Monteleone writes:
> I seem to recall a development goal being to eliminate Scheme code
> except for reports.
>
> This might be a good candidate for just re-writing this in C/C++ with
> proper tests and verbose error output and/or logging.
>
> If someone with the skillset is intereste
Cool. I tried similar to what you did, but didn't understand where to put the
aqbaning-cli param (versions) -- not too intuitive...
Yeah, I know, RTFM...
> On Feb 19, 2020, at 10:07 AM, Geert Janssens
> wrote:
>
> flatpak run --command=aqbanking-cli org.gnucash.GnuCash versions
___
It took me a while to figure it out as well. While I'm currently maintaining
the flatpak
for gnucash I'm far from mastering the whole system.
I personally find its documentation fairly sparse :(
Geert
Op woensdag 19 februari 2020 20:06:30 CET schreef chris graves:
> Cool. I tried similar to w
Qif importer does have special handling for empty categories. Changing this
is likely to break things elsewhere though.
It would be useful to attach the minimal qif file from selective qif export
from quicken, and insert screenshots from quicken too. Maybe best file bug
in Bugzilla.
__
I looked at the trace file being produced in /tmp/gnucash.trace,
but it did not seem to help any.
I added (gnc:pk ...) messages, but none of them ever
appeared.
I added (pk ...) lines to qif-to-gnc.scm to try to trace
what it was doing. This produced a large amount of output
on the terminal, bu
13 matches
Mail list logo
