> On Oct 24, 2014, at 7:29 AM, Derek Atkins wrote:
>
> John Ralls writes:
>
>> On Oct 23, 2014, at 9:25 AM, Derek Atkins wrote:
>>
>>> John Ralls writes:
>>>
> I'm not sure this is possible in guile only. A report is written as
> a guile module. Loading the module already executes
John Ralls writes:
> On Oct 23, 2014, at 9:25 AM, Derek Atkins wrote:
>
>> John Ralls writes:
>>
I'm not sure this is possible in guile only. A report is written as
a guile module. Loading the module already executes code
(gnc:define-report). That code can be abused do bad thing
On Oct 23, 2014, at 9:25 AM, Derek Atkins wrote:
> John Ralls writes:
>
>>> I'm not sure this is possible in guile only. A report is written as
>>> a guile module. Loading the module already executes code
>>> (gnc:define-report). That code can be abused do bad things when
>>> loading a custom
John Ralls writes:
>> I'm not sure this is possible in guile only. A report is written as
>> a guile module. Loading the module already executes code
>> (gnc:define-report). That code can be abused do bad things when
>> loading a custom report.
>
> Wow. That’s an incredible failure for something
On Oct 21, 2014, at 9:27 AM, Geert Janssens wrote:
> I have moved this thread from gnucash-user as it was getting rather
> technical...
>
> On Tuesday 21 October 2014 08:43:04 John Ralls wrote:
> > > >
> > > > One possible solution is to get Guile out of the file-opening
> > > > loop.
> > >
I have moved this thread from gnucash-user as it was getting rather technical...
On Tuesday 21 October 2014 08:43:04 John Ralls wrote:
> > >
> > > One possible solution is to get Guile out of the file-opening
> > > loop.
> > > Having a configuration file that’s directly executed by Guile is a
> >
