Thanks!
Regards,
Adrien
> On Sep 10, 2019 w37d253, at 1:36 PM, Geert Janssens
> wrote:
>
> In gnucash 3.x all uses of gnucash printf have been replaced with guile's own
> "format" function [1]. The printf hack was calling the c-function printf,
> which is adding overhead for no gain.
>
> T
In gnucash 3.x all uses of gnucash printf have been replaced with guile's own
"format" function [1]. The printf hack was calling the c-function printf,
which is adding overhead for no gain.
The same conversion from printf to (format ) will have to be applied to Doug's
reports.
Regards,
Geert
See my other reply on how to get meaningful info in the terminal.
When a report fails, it will prevent loading of all reports in that
config-user.scm file.
You can comment individual load lines out with an initial semicolon like so:
;(load (gnc-build-userdata-path "John-Report.scm”))
And that
cat $TMPDIR/gnucash.trace
will show some info, but as I noted in the first post, not enough to determine
which report(s) are the problem.
However, running GnuCash from the terminal like so:
/Applications/Gnucash.app/Contents/MacOS/Gnucash --debug --log gnc.scm=debug
Will generate more info tha
Hi John,
As you suggest this is likely due to errors in the report code. If so there
should be more details either in the gnucash trace file or on the console. I'm
not on Macos so I'm not sure where console messages get written for
applications that are launched from the gui.
You may be able to
Hi Adrien,
I worked my way through the GnuCash wiki on loading custom reports at
https://wiki.gnucash.org/wiki/Custom_Reports#Where_to_find_existing_reports. I
made a tiny bit of headway, but not much.
I have set up a new file called config-user.scm in ~/Library/Application
Support/GnuCash
I didn’t get to test #1 & #2 again, but sticking with #3, I started GnuCash with
--debug --log gnc.scm=debug
And got some useful info.
It seems all but one of the reports were using:
(use-modules (gnucash main))
which apparently doesn’t exist any more.
The one report that did work was using:
Spurred by another thread concerning carrying over custom reports from 2.6.x to
3.x, I finally decided to get around to doing the same for my own. I’ve grabbed
several reports from the mailing list over the years that I was testing and
playing with from 2.6.x and would like to get them working a
