- Dillo-dev - lists.mailman3.com

valgrind errors

by sgeerken＠dillo.org

On Mi, Jun 22, 2016, eocene wrote: > Another one is containerAllocationState not getting initialized in > OOFPositionedMgr. Fixed, too. Sebastian

June 26, 2016

valgrind errors

by sgeerken＠dillo.org

On Mi, Jun 22, 2016, eocene wrote: > > Was just having a look at the valgrind errors, and I think the > main one is in textblock.cc: > > int leftBorder = boxOffsetX () + leftInnerPadding > + (lines->size () == 0 ? line1OffsetEff : 0); > > leftBorder being set to line1OffsetEff when line1OffsetEff > has not been initialized. Fixed. (With one open issue which has been an open issue for a long time.) Sebastian

June 26, 2016

Error message when starting 3.1-dev from xterm

by eocene＠gmx.com

waltdnes wrote: > Changing that line to start with "#" instead of "*" gets rid of the > error. Fixed the typo, and I changed the error msg to print the line number.

June 26, 2016

Error message when starting 3.1-dev from xterm

by waltdnes＠waltdnes.org

On Sat, Jun 25, 2016 at 07:02:13AM +0000, eocene wrote > waltdnes wrote: > > Wnen starting up from an xterm, and then exiting, I get the > > following. > > > > ** ERROR **: prefsparser: Syntax error in dillorc: name="(null)" value="(null)" > > Domain: Default accept. > > dillo_dns_init: Here we go! (threaded) > > Disabling cookies. > > Dillo: normal exit! > > > > I moved my custom dillorc, and copied the generic one, i.e. > > > > /usr/local/dillo/etc/dillo/dillorc > > > > to check that it wasn't something I did. It still gets the same error. > > It looks like dParser_parse_rc_line() does not deal > very well with the case where the line is not empty, > is not a comment, and lacks an '='. BINGO! cd .dillo grep -v "=" dillorc | grep -v "^#" > z.txt .dillo/z.txt contains a bunch of blank lines, plus the line... * HSTS directives are not saved between browser sessions. Changing that line to start with "#" instead of "*" gets rid of the error. -- Walter Dnes <waltdnes at waltdnes.org>

June 25, 2016

Patch: Zero detected HTML errors

by nick＠linicks.net

On Sat, 25 Jun 2016 11:57:06 -0400 Jorge Arellano Cid <jcid at dillo.org> wrote: > On Sat, Jun 25, 2016 at 01:56:14PM +0100, Nick Warne wrote: > > On Fri, 24 Jun 2016 17:13:59 -0400 > > Jorge Arellano Cid <jcid at dillo.org> wrote: > > > > > OK, let's take a look at this one. > > > > > > The idea is to inform that the bug meter detected zero HTML > > > errors, not that the doc is perfect (because the bug meter checks > > > a subset of the syntax/grammar legalese). > > > > > > How is that best expressed in english? > > > > > > > - a_Dialog_msg("Dillo: Valid HTML!", "Zero detected HTML > > > > errors!"); > > > > + a_Dialog_msg("Dillo: Valid HTML!", "Detected no HTML > > > > errors!"); > > > > Well, lets suppose that someone is called 'Zero'. > > > > "Zero detected HTML errors!" > > > > implies that he/she detected errors! > > Thanks. This makes it clear to me. > > > > > What about: "Could not detect any HTML errors!" > > > > which then implies that the current bug meter thinks it's OK (but > > as we know, there _still_ may be HTML errors. > > One more question, why not? > > 1. "No HTML errors detected!" or > > 2. "Zero HTML errors detected!" or > > 3. "Detected zero HTML errors!" > > > ** If I choose by replacing pronouns I'd have: > > 1. "He" detected! > 2. "He" detected! > 3. Dtected him! > > I'd choose 3.- as 1.- and 2.- are wrong. Am I right? OK, why not make it what it is: "Dillo Bug meter: no HTML errors detected" and also: "Dillo Bug meter: HTML errors detected" Pretty trivial stuff, but at least the viewer gets what you see. Nick -- Gosh that takes me back... or is it forward? That's the trouble with time travel, you never can tell." -- Doctor Who "Androids of Tara"

June 25, 2016

Patch: Zero detected HTML errors

by jcid＠dillo.org

On Sat, Jun 25, 2016 at 01:56:14PM +0100, Nick Warne wrote: > On Fri, 24 Jun 2016 17:13:59 -0400 > Jorge Arellano Cid <jcid at dillo.org> wrote: > > > OK, let's take a look at this one. > > > > The idea is to inform that the bug meter detected zero HTML errors, > > not that the doc is perfect (because the bug meter checks a subset of > > the syntax/grammar legalese). > > > > How is that best expressed in english? > > > > > - a_Dialog_msg("Dillo: Valid HTML!", "Zero detected HTML > > > errors!"); > > > + a_Dialog_msg("Dillo: Valid HTML!", "Detected no HTML > > > errors!"); > > Well, lets suppose that someone is called 'Zero'. > > "Zero detected HTML errors!" > > implies that he/she detected errors! Thanks. This makes it clear to me. > > What about: "Could not detect any HTML errors!" > > which then implies that the current bug meter thinks it's OK (but as we > know, there _still_ may be HTML errors. One more question, why not? 1. "No HTML errors detected!" or 2. "Zero HTML errors detected!" or 3. "Detected zero HTML errors!" ** If I choose by replacing pronouns I'd have: 1. "He" detected! 2. "He" detected! 3. Dtected him! I'd choose 3.- as 1.- and 2.- are wrong. Am I right? -- Cheers Jorge.-

June 25, 2016

Error message when starting 3.1-dev from xterm

by nick＠linicks.net

On Sat, 25 Jun 2016 07:02:13 +0000 eocene <eocene at gmx.com> wrote: > waltdnes wrote: > > Wnen starting up from an xterm, and then exiting, I get the > > following. > > > > ** ERROR **: prefsparser: Syntax error in dillorc: name="(null)" > > value="(null)" Domain: Default accept. > > dillo_dns_init: Here we go! (threaded) > > Disabling cookies. > > Dillo: normal exit! > > > > I moved my custom dillorc, and copied the generic one, i.e. > > > > /usr/local/dillo/etc/dillo/dillorc > > > > to check that it wasn't something I did. It still gets the same > > error. > > It looks like dParser_parse_rc_line() does not deal > very well with the case where the line is not empty, > is not a comment, and lacks an '='. Strange, I don't get that warning on the default dillorc nor on my $HOME/.dillo/dillorc? Nick -- Gosh that takes me back... or is it forward? That's the trouble with time travel, you never can tell." -- Doctor Who "Androids of Tara"

June 25, 2016

Patch: Zero detected HTML errors

by nick＠linicks.net

On Fri, 24 Jun 2016 17:13:59 -0400 Jorge Arellano Cid <jcid at dillo.org> wrote: > OK, let's take a look at this one. > > The idea is to inform that the bug meter detected zero HTML errors, > not that the doc is perfect (because the bug meter checks a subset of > the syntax/grammar legalese). > > How is that best expressed in english? > > > - a_Dialog_msg("Dillo: Valid HTML!", "Zero detected HTML > > errors!"); > > + a_Dialog_msg("Dillo: Valid HTML!", "Detected no HTML > > errors!"); Well, lets suppose that someone is called 'Zero'. "Zero detected HTML errors!" implies that he/she detected errors! What about: "Could not detect any HTML errors!" which then implies that the current bug meter thinks it's OK (but as we know, there _still_ may be HTML errors. Nick -- Gosh that takes me back... or is it forward? That's the trouble with time travel, you never can tell." -- Doctor Who "Androids of Tara"

June 25, 2016

Error message when starting 3.1-dev from xterm

by eocene＠gmx.com

waltdnes wrote: > Wnen starting up from an xterm, and then exiting, I get the > following. > > ** ERROR **: prefsparser: Syntax error in dillorc: name="(null)" value="(null)" > Domain: Default accept. > dillo_dns_init: Here we go! (threaded) > Disabling cookies. > Dillo: normal exit! > > I moved my custom dillorc, and copied the generic one, i.e. > > /usr/local/dillo/etc/dillo/dillorc > > to check that it wasn't something I did. It still gets the same error. It looks like dParser_parse_rc_line() does not deal very well with the case where the line is not empty, is not a comment, and lacks an '='.

June 25, 2016

Error message when starting 3.1-dev from xterm

by waltdnes＠waltdnes.org

Wnen starting up from an xterm, and then exiting, I get the following. ** ERROR **: prefsparser: Syntax error in dillorc: name="(null)" value="(null)" Domain: Default accept. dillo_dns_init: Here we go! (threaded) Disabling cookies. Dillo: normal exit! I moved my custom dillorc, and copied the generic one, i.e. /usr/local/dillo/etc/dillo/dillorc to check that it wasn't something I did. It still gets the same error. -- Walter Dnes <waltdnes at waltdnes.org>

June 25, 2016