Re: report in python, a first version

On Nov 16, 2016 12:30 AM, "John Ralls" wrote: > > > > On Nov 15, 2016, at 12:58 PM, Sébastien de Menten wrote: > > > > > > On Tue, Nov 15, 2016 at 6:41 PM, John Ralls wrote: > > > > > On Nov 15, 2016, at 9:24 AM, Sébastien de Menten

RE: Lots in Account screen : Value sign

Re https://bugzilla.gnome.org/show_bug.cgi?id=770364 Currently the Lots in Account screen reverses the sign of the value shown in all the splits in the Splits Free and Splits in Lot panels, except the first. The reason this was done seems to be that because each buy has a unique lot, the first

Re: Nightly Documentation Builds

Hi, Sorry, I should have mentioned it (but I've been busy) --- the docs build is broken. It takes manual effort to get the error, I only get a "build failed" email (which literally says "gnucash-docs build failed" and nothing more). I'll try to go take a look tonight. -derek On Wed, November

RE: Bug advice, and XML markup assistance

> Message: 5 > Date: Wed, 16 Nov 2016 18:28:38 +0500 > From: "David T." > To: "David T. via gnucash-devel" > Subject: Bug advice, and XML markup assistance > Message-ID: > Content-Type: text/plain;

Re: Nightly Documentation Builds

Huh.. I just ran it by hand and it worked... Not sure why the nightly failed. I'm trying it again. -derek On Wed, November 16, 2016 8:16 pm, Derek Atkins wrote: > Hi, > > Sorry, I should have mentioned it (but I've been busy) --- the docs build > is broken. It takes manual effort to get the

Nightly Documentation Builds

Hi, Re Lots in Account documentation. The guide was updated the day after my PR was merged (I think) but the help (http://code.gnucash.org/docs/C/gnucash-help.pdf) was merged Nov 14 and has not been updated yet. Is there something wrong with the Nightly Doc Builds or is it not automatic?

Re: report in python, a first version

> On Nov 16, 2016, at 2:19 PM, Sébastien de Menten wrote: > Still hoping *complexity* is not considered a feature ;-) > > > It's the html string that I'm particularly worried about, because that gets > > you to a well-known library with lots of well-known and

Re: Bug advice, and XML markup assistance

Chris, Thanks for the input, and the suggestion to look at the investments chapter. That’s a good lead. The bug in question is Bug 743671. Sorry I didn’t include that originally. And, yes, it is a bug that I submitted myself. David > On Nov 17, 2016, at 6:06 AM, Chris Good

Bug advice, and XML markup assistance

Hi, I was looking through the documentation bugs, and saw the request for a new Glossary for the docs, and I have a few questions. First, does this in fact appear to be a good idea? Or is it a waste of time? If the latter, perhaps the existing glossary on the wiki and various references to a