- Dillo-dev - lists.mailman3.com

Changes at hg.dillo.org - now I cannot access the repository

by onepoint＠starurchin.org

I noticed that my connections to hg.dillo.org were timing out. I discovered that the IP address had changed and so my firewall was dropping the packets. So I updated my firewall to fix that, and now my connections are immediately rejected. For instance, if I try "hg incoming" it immediately responds "abort: error: Connection refused" and exits with status 255 (which I take to mean that something serious went wrong). So what to do to fix this? Adding a "--verbose" flag to the "hg incoming" command did not change the output. Maybe the port 39390 which is specified in my repository's hgrc file is no longer correct, but I do not know how to test that. Any ideas? Regards, Jeremy Henty

March 22, 2017

dillo dev with https

by andreas＠kemnade.info

Hi, On Sat, 4 Feb 2017 12:20:07 +0000 Adam Mendoza <adammendoza at hotmail.com> wrote: > Can someone do a quick Skype or similar to get a build set-up with > https? I want to be a contributor. > well, its just es usual, there are libpng, libjpeg, libfltk-1.3 and libmbedtls as dependencies. You have to install their development headers. Hint for debian jessie: libmbedtls-dev is in jessie-backports. And then the usual autogen.sh, configure --enable-ssl, make, make install Regards, Andreas Kemnade

Feb. 4, 2017

[Correction] Any plans for a release in the next few weeks?

by jcid＠dillo.org

On Mon, Dec 05, 2016 at 05:52:21PM +0100, Axel Beckert wrote: > Hi, > > On Mon, Dec 05, 2016 at 01:45:36AM +0100, Axel Beckert wrote: > > since the freeze for the next Debian Stable release is quite close, I > > wonder if there are any plans for a new Dillo release in the next few > > weeks. > [...] > > The freeze for new upstream versions is on 5th of January 2017 and to > > be included, new upstream releases must have migrated from Debian > > Unstable to Debian Testing before that date. > > I mixed up things a little bit here. The relevant date here is the 5th > of February. The earlier soft freeze is only relevant for packages not > yet in Debian. Sorry for mixing up those dates. > > > Given the 10 days migration period, the last chance for an upload > > would be on 2016-12-24, preferable earlier so that there's a chance > > to fix potential issues like unexpected build failures, etc. in > > time. > > So that date is now 2017-01-24. Thanks Axel for letting us know these dates. Almost certainly it'll be packed and released before that date. (the last of the dillo 3.x series) The next release (dillo 4.x) will feature a new rendering engine. I'm currently 100% busy with other rather pressing issues outside the dillo realm, but in 2017 it will be different. -- Cheers Jorge.-

Dec. 7, 2016

[Correction] Any plans for a release in the next few weeks?

by abe＠deuxchevaux.org

Hi, On Mon, Dec 05, 2016 at 01:45:36AM +0100, Axel Beckert wrote: > since the freeze for the next Debian Stable release is quite close, I > wonder if there are any plans for a new Dillo release in the next few > weeks. [...] > The freeze for new upstream versions is on 5th of January 2017 and to > be included, new upstream releases must have migrated from Debian > Unstable to Debian Testing before that date. I mixed up things a little bit here. The relevant date here is the 5th of February. The earlier soft freeze is only relevant for packages not yet in Debian. Sorry for mixing up those dates. > Given the 10 days migration period, the last chance for an upload > would be on 2016-12-24, preferable earlier so that there's a chance > to fix potential issues like unexpected build failures, etc. in > time. So that date is now 2017-01-24. Kind regards, Axel -- /~\ Plain Text Ribbon Campaign | Axel Beckert \ / Say No to HTML in E-Mail and News | abe at deuxchevaux.org (Mail) X See http://www.nonhtmlmail.org/campaign.html | abe at noone.org (Mail+Jabber) / \ I love long mails: http://email.is-not-s.ms/ | http://abe.noone.org/ (Web)

Dec. 5, 2016

Any plans for a release in the next few weeks?

by abe＠deuxchevaux.org

Dear Dillo Developers, since the freeze for the next Debian Stable release is quite close, I wonder if there are any plans for a new Dillo release in the next few weeks. If so, I'd be happy if that release (epsecially if there will be a 3.0.6) would happen before christmas to be able to get it into the next Debian Stable release. (I currently assume that 3.1 won't be ready before christmas, but feel free to surprise me. ;-) The freeze for new upstream versions is on 5th of January 2017 and to be included, new upstream releases must have migrated from Debian Unstable to Debian Testing before that date. Given the 10 days migration period, the last chance for an upload would be on 2016-12-24, preferable earlier so that there's a chance to fix potential issues like unexpected build failures, etc. in time. P.S.: Releasing the next Debian Stable with a well-working 3.0.5 isn't bad either. Just wanting to let you know about these freeze deadlines. Kind regards, Axel -- /~\ Plain Text Ribbon Campaign | Axel Beckert \ / Say No to HTML in E-Mail and News | abe at deuxchevaux.org (Mail) X See http://www.nonhtmlmail.org/campaign.html | abe at noone.org (Mail+Jabber) / \ I love long mails: http://email.is-not-s.ms/ | http://abe.noone.org/ (Web)

Dec. 5, 2016

Cannot log into github

by jcid＠dillo.org

On Tue, Nov 01, 2016 at 10:52:29PM +0000, Stephen Paul Weber wrote: > Can others log into Github with Dillo tip? I just built and installed and > while I no longer see errors about cookie date formats with tip like I did > with the version I had installed, it still does not log me in. > > I am using two factor auth with Github, in case that make a difference > compared to anyone else's experience. > > Thanks for any help :) I haven't used github, maybe somebody else can help here. -- Cheers Jorge.-

Nov. 2, 2016

Cannot log into github

by singpolyma＠singpolyma.net

Can others log into Github with Dillo tip? I just built and installed and while I no longer see errors about cookie date formats with tip like I did with the version I had installed, it still does not log me in. I am using two factor auth with Github, in case that make a difference compared to anyone else's experience. Thanks for any help :) -- Stephen Paul Weber, @singpolyma See <http://singpolyma.net> for how I prefer to be contacted edition right joseph

Nov. 1, 2016

Page sneds Dillo into a (lock up] loop

by nick＠linicks.net

Hi all, Chin-up people :) Believe it or not, I was looking into HTML5 font size stuff, and found Dillo seemed to crash on the page below. Running raw from a terminal that is not the case - it gets it's knickers in a twist in a permanent loop of: ... Layout::resizeIdle calls = 2536 Layout::resizeIdle calls = 2537 Layout::resizeIdle calls = 2538 Layout::resizeIdle calls = 2539 Layout::resizeIdle calls = 2540 Layout::resizeIdle calls = 2541 Layout::resizeIdle calls = 2542 Layout::resizeIdle calls = 2543 Layout::resizeIdle calls = 2544 Layout::resizeIdle calls = 2545 Layout::resizeIdle calls = 2546 Layout::resizeIdle calls = 2547 Layout::resizeIdle calls = 2548 Layout::resizeIdle calls = 2549 etc. The link (BEWARE!): http://www.w3schools.com/cssref/pr_font_font-size.asp 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"

Oct. 30, 2016

Gmail textareas

by james.from.wellington＠gmail.com

Hi All, I'm not sure whether Google changed things or I forgot the scope of my work-around. Here's a different one (still a .gdbinit) that's equally crude but possibly more robust: -------------- break CSS_CREATE_LENGTH(float, CssLengthType) cond 1 (t==CSS_LENGTH_TYPE_EX) commands 1 print t=CSS_LENGTH_TYPE_PERCENTAGE print v=100 cont -------------- Regards, James. On 21/10/2016, James C <james.from.wellington at gmail.com> wrote: > Hello all, > > I have a work-around, so this isn't urgent. In view of recent events, > keep caring for yourselves. > > Gmail sizes some text areas weirdly, as (CSS) width:80ex, and they > disappear from view. I've tried two fonts, and the disappearance is > complete in both cases. A cut down example is attached. The diff to > suppress the disappearance is: > > --- gmail-compose-14.html 2016-10-21 21:06:01.000000000 +1300 > +++ gmail-compose-15.html 2016-10-21 21:10:41.000000000 +1300 > @@ -18,7 +18,10 @@ > .th a:link, .th a:active, .th a:visited{text-decoration:none} > .bn td{border:1px solid #FAD163} > .ct textarea, .ct input, .ct > select{font-family:arial,sans-serif;font-size:100%} > + > .compose .mi{width:80ex;font-family:arial,sans-serif;font-size:100%} > +.compose .mi{width:100%;font-family:arial,sans-serif;font-size:100%} > + > .compose .i, .search > .i{width:99%;font-family:arial,sans-serif;font-size:100%} > .qr textarea{width:80ex;font-family:arial,sans-serif;font-size:100%} > .qr input{font-family:arial,sans-serif;font-size:100%} > > > The immensely crude work-around is the following, as a .gdbinit: > ---------------- > break 'StyleEngine::setClass' > break main > commands 2 > cond 1 (0 == (int)strcmp(klass, "mi")) > cont > end > commands 1 > set klass = "i" > cont > end > run > ---------------- > > I'm open to hints about where to look for the effect of width on > multiline text resources, but really I'm lost. > > Regards, > James. >

Oct. 24, 2016

Gmail textareas

by james.from.wellington＠gmail.com

Hello all, I have a work-around, so this isn't urgent. In view of recent events, keep caring for yourselves. Gmail sizes some text areas weirdly, as (CSS) width:80ex, and they disappear from view. I've tried two fonts, and the disappearance is complete in both cases. A cut down example is attached. The diff to suppress the disappearance is: --- gmail-compose-14.html 2016-10-21 21:06:01.000000000 +1300 +++ gmail-compose-15.html 2016-10-21 21:10:41.000000000 +1300 @@ -18,7 +18,10 @@ .th a:link, .th a:active, .th a:visited{text-decoration:none} .bn td{border:1px solid #FAD163} .ct textarea, .ct input, .ct select{font-family:arial,sans-serif;font-size:100%} + .compose .mi{width:80ex;font-family:arial,sans-serif;font-size:100%} +.compose .mi{width:100%;font-family:arial,sans-serif;font-size:100%} + .compose .i, .search .i{width:99%;font-family:arial,sans-serif;font-size:100%} .qr textarea{width:80ex;font-family:arial,sans-serif;font-size:100%} .qr input{font-family:arial,sans-serif;font-size:100%} The immensely crude work-around is the following, as a .gdbinit: ---------------- break 'StyleEngine::setClass' break main commands 2 cond 1 (0 == (int)strcmp(klass, "mi")) cont end commands 1 set klass = "i" cont end run ---------------- I'm open to hints about where to look for the effect of width on multiline text resources, but really I'm lost. Regards, James.

Oct. 21, 2016