- Dillo-dev - lists.mailman3.com

How to link to a specific bug report?
by abe＠deuxchevaux.org Dec. 24, 2012

Dec. 24, 2012

Hi, I just submitted a (forwarded) bug report (#1113) and would like to link to it directly. Is there any query string parameter where I can enter the bug number? Neither "bug_number" like for the volunteer and remove CGI scripts does work nor does what=1113. In case there isn't such a featre yet, I'd be happy if you could at least e.g. <a name="1113">...</a> jump mark. Thta should be quite easy with regards to the CGI script's current output. TIA. 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.asciiribbon.org/ | abe at noone.org (Mail+Jabber) / \ I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web)

2 2

Extensions for hyphenation
by sgeerken＠dillo.org Dec. 23, 2012

Dec. 23, 2012

Hi! At http://flpsed.org/hgweb/dillo_hyphen, you'll find some extensions for hyphenation I've not yet merged into the main repository. Still needs some documentation, but here is an overview: There are now configuration variables for dillorc (see source): penalties for hyphens, as well as the left and right side of an em-dash. The suffix "_2" means that this value is used for lines following a line which ends already with a hyphen. When this value is larger, two adjacent lines ending with a hyphen are avoided. For values, see the definition of the "badness". Typical values: 0 = Penalty used for normal spaces. 1 = A justified line with spaces having 150% or 67% of the ideal space width has this as badness. 8 = A justified line with spaces twice as wide as ideally has this as badness. "inf" may be used (preventing a break in any case); also "-inf" (forcing a break), although the latter makes no sense and may lead to strange results. There is a text page, test/hyphens-etc.html, to play around. Sebastian

4 21

[patch] dns.c: missing break in a_Dns_dillohost_to_string
by p37sitdu＠lavabit.com Dec. 20, 2012

Dec. 20, 2012

Fix is attached.

2 1

config.h.in and configure.in
by onepoint＠starurchin.org Dec. 20, 2012

Dec. 20, 2012

I thought that we agreed[1] to remove config.h.in from the repository and to rename configure.in to configure.ac . Can I make these changes or is more discussion needed? Regards, Jeremy Henty [1]: http://lists.auriga.wearlab.de/pipermail/dillo-dev/2012-December/009618.html

2 2

[patch] send_dpip_tag in vsource.c is unused
by p37sitdu＠lavabit.com Dec. 20, 2012

Dec. 20, 2012

Attached patch removes unused function send_dpip_tag. Functions send_plain_text, send_numbered_text and send_html_text are made static.

1 0

dpid patches
by p37sitdu＠lavabit.com Dec. 18, 2012

Dec. 18, 2012

First patch is for removing expired TODO item, just resending it. Second patch is new, for dpid.c. Function fill_services_list has a bug: on line 463 there is a check *services_list != NULL. If it is true, then -1 is returned, but dpidrc_stream is not closed. Error message on line 456 says "popen failed", should be "fopen failed". fill_services_list checks for availability of user_dpidir and sys_dpidir, but after line 449 these variables are not used. They are just dFreed in the end. Looks like code was just copypasted from register_all. fill_services_list is only called from main.c:248 and dpid.c:807 of dpid.c. register_all is called from main.c:235 and dpid.c:806. So fill_services_list is always called after register_all and doing the same check is useless. On line 503 there is a conversion of services_alpha_comp to type (dCompareFunc). I changed the function services_alpha_comp to the usual style of writing comparison functions so no conversion is required. In the current state it is undefined behaviour. [1] [1] http://stackoverflow.com/questions/559581/casting-a-function-pointer-to-ano…

1 0

[patch] Gopher DPI
by p37sitdu＠lavabit.com Dec. 17, 2012

Dec. 17, 2012

I implemented basic Gopher support using DPI, patch is attached. It is already quite usable. "URL:" links are not supported, but Gopher servers send redirect pages for compatibility. The only major problem is unrecognized file types. I looked at FTP DPI. It sends Content-type: application/octet-stream. This forces Dillo to ask downloads DPI to start download. With gopher it doesn't work as downloads DPI doesn't suppport gopher. So Dillo just says "Content-Type 'application/octet-stream' not viewable.". I left it as it is for now, because I don't think adding support for all known and unknown protocols into downloads.cc is the right solution. Maybe downloads DPI protocol should be changed so Dillo would feed plugin with data it receives as octet-stream and downloads DPI would only save what it receives to disk instead of connecting to server and downloading the file itself.

4 9

Tooltip bugs revisited
by jcid＠dillo.org Dec. 17, 2012

Dec. 17, 2012

Hi there, These days I've devoted some more effort to the tooltips bug [1] and its workaround patch [2]. The motivation is that the current workaround involves a full UI and viewport expose (i.e. a full erase/redraw) that produces annoying flickering when the mouse is in the UI but outside the viewport (e.g. over the panel). Over time I've learnt to move the mouse pointer outside the panel and into the viewport to scroll without flickering (but probably I'm among the few that know this trick). So far (and despite the warning inside FLTK), I've experimented with a custom tooltip handling class, and a couple custom UI widgets, that seem to work well together (i.e. solve the problem without the workaround :) ). Testing revealed the workaround concealed another problem, which I don't remember whether it was detected before, and this is that viewport mouse events get "through" the panel UI!. How?, placing the mouse pointer over the panel (e.g. to the right of the Tools button, or even inside the Location), and scrolling a page full of links under it, will make the mouse pointer change to a hand, and the destination link appear in the status bar area. This bug is revealed by disabling the workaround: just apply the small attached patch. Clearly there's a viewport offset problem somewhere. Correcting it may save us lots of headaches in the future. Does anybody know or has a clue of where this may be happening? TIA. [1] http://lists.auriga.wearlab.de/pipermail/dillo-dev/2011-July/008494.html [2] http://lists.auriga.wearlab.de/pipermail/dillo-dev/2011-July/008515.html -- Cheers Jorge.-

2 6

Fwd: Re: Dillo early exit
by sgeerken＠dillo.org Dec. 15, 2012

Dec. 15, 2012

Somehow this post got lost ...

3 3

config.h.in
by p37sitdu＠lavabit.com Dec. 14, 2012

Dec. 14, 2012

^config\. is in .hgignore, bug config.h.in is tracked. It is autogenerated, shouldn't it be removed from repo?

4 7