Op dinsdag 8 januari 2019 01:31:58 CET schreef Alex Aycinena:
> Geert,
>
> On Sun, Jan 6, 2019 at 9:17 AM Alex Aycinena
>
> wrote:
> > Geert,
> >
> > On Sun, Jan 6, 2019 at 8:11 AM Geert Janssens
> >
> > wrote:
> >> On Sunday, January 6, 2019 4:55:09 AM CET Alex Aycinena wrote:
> >> > Geert,
Geert,
On Sun, Jan 6, 2019 at 9:17 AM Alex Aycinena
wrote:
> Geert,
>
> On Sun, Jan 6, 2019 at 8:11 AM Geert Janssens
> wrote:
>
>> On Sunday, January 6, 2019 4:55:09 AM CET Alex Aycinena wrote:
>> > Geert,
>> >
>> > I have been investigating bug # 796687 (Tax Entity name and type for an
>> > a
Geert,
On Sun, Jan 6, 2019 at 8:11 AM Geert Janssens
wrote:
> On Sunday, January 6, 2019 4:55:09 AM CET Alex Aycinena wrote:
> > Geert,
> >
> > I have been investigating bug # 796687 (Tax Entity name and type for an
> > account won't work under "Tax Reporting Options" in Gnucash 3.2) and it
> >
On Sunday, January 6, 2019 4:55:09 AM CET Alex Aycinena wrote:
> Geert,
>
> I have been investigating bug # 796687 (Tax Entity name and type for an
> account won't work under "Tax Reporting Options" in Gnucash 3.2) and it
> seems that your commit 4053f2ca5331b345f04f75022658d254c36bdd15 on Mar 31,
Geert,
I have been investigating bug # 796687 (Tax Entity name and type for an
account won't work under "Tax Reporting Options" in Gnucash 3.2) and it
seems that your commit 4053f2ca5331b345f04f75022658d254c36bdd15 on Mar 31,
2018, has caused book string options not to work. I ran gnucash under gd
