A crucial GNUCash feature that is missing, but easy to implement for budgets

[Geert Janssens]

Op woensdag 18 januari 2017 19:47:03 CET schreef David T.:
> Clearing the cache doesn’t help, although removing the report from loading
> does remove these errors, so I think it is fair to say that whatever it is
> preventing the report from loading into the menus, it has to do with
> something in the report itself.
> 
> Thanks,
> David
> 
With some delay...

I'm actually not convinced the problem is in the report itself. In earlier 
posts you said it works fine when you add it directly in the standard-reports 
directory. Which suggests
- either the issue rather is in your user.conf file
- or is due to a different code path being followed when loading reports from 
the standard-reports directory versus loading it directly from user.conf.

Can you provide me a copy of both files ? That is, the report as you are using 
it and a user.conf with the load line that fails.

Regards,

Geert

> > On Jan 18, 2017, at 2:27 AM, John Ralls <jralls at ceridwen.us> wrote:
> >> On Jan 17, 2017, at 10:21 AM, Geert Janssens <geert.gnucash at kobaltwit.be>
> >> wrote:>> 
> >> Op dinsdag 17 januari 2017 22:34:00 CET schreef David T.:
> >>> ERROR: In procedure apply-smob/1:
> >>> ERROR: In procedure scm_from_stringn: Error while printing exception.
> >>> In ice-9/boot-9.scm:
> >>> 157: 7 [catch #t #<catch-closure d18d640> ...]
> >>> 
> >>> In unknown file:
> >>>  ?: 6 [apply-smob/1 #<catch-closure d18d640>]
> >>> 
> >>> In ice-9/boot-9.scm:
> >>> 157: 5 [catch #t #<catch-closure e3348e0> #<catch-closure e3348d0> #f]
> >>> 
> >>> In unknown file:
> >>>  ?: 4 [apply-smob/1 #<catch-closure e3348e0>]
> >>> 
> >>> In ice-9/boot-9.scm:
> >>> 171: 3 [with-throw-handler #t #<catch-closure e334870> #<catch-closure
> >>> 
> >>> e334860>] In unknown file:
> >>>  ?: 2 [apply-smob/1 #<catch-closure e334870>]
> >>> 
> >>> In ice-9/boot-9.scm:
> >>> 102: 1 [#<procedure d8461c0 at ice-9/boot-9.scm:97:6 (thrown-k . args)>
> >>> 
> >>> decoding-error ...] In unknown file:
> >>>  ?: 0 [apply-smob/1 #<catch-closure e334860> decoding-error ...]
> >> 
> >> Hi David,
> >> 
> >> I'm afraid I've never seen this before. The way I interpret is that while
> >> attempting to load the report guile encounters an error and wants to
> >> throw an exception. I don't know which exception that is because this
> >> triggers another error due to which the trace can't be printed properly.
> >> This error a 'decoding-error'. So from the little info available here it
> >> seems guile encounters an invalid character somewhere while trying to
> >> load this report. I'm afraid I don't know where or why.
> >> 
> >> One final thing to try is to clear the guile compile cache. Unfortunately
> >> I
> >> don't know either where this is located on OS X. Perhaps John can help
> >> with
> >> this.
> > 
> > The user's cache is in ~/.caches/guile.
> > 
> > Regards,
> > John Ralls