July 2014 - Dillo-dev - lists.mailman3.com

Dillo and Irix
by diegel＠work.de 25 Sep '14

25 Sep '14

Hello, I just started another attempt to port dillo to Irix. With gcc 4.7 it compiles without any serious warnings. It starts and about:splash shows up correctly, But if you want to use it something goes wrong: ftp works without problems. files show up if the path is very short (less than 32 bytes). If you browse directories and you want to change from /tmp to /tmp/x for example. I changes to /x http doesn't work at all. If you go to a non existing url. For example: http://test.yy you get the following console output, but nothing happens in the dollo window: Nav_open_url: new url='http:test.yy' a_Capi_ccc : OpStart [2B] Info=10262fa8 Flags=0 a_Dpi_ccc : OpStart [2B] Info=10262da0 Flags=0 a_IO_ccc : OpStart [2B] Info=10262e90 Flags=0 a_Capi_ccc : OpStart [1B] Info=10262eb8 Flags=0 a_Http_ccc : OpStart [1B] Info=10262f80 Flags=0 a_IO_ccc : OpStart [1B] Info=10262e40 Flags=0 Http_must_use_proxy: http:test.yy NO DNS error: HOST_NOT_FOUND Dns_server [0]: is (nil) a_IO_ccc : OpAbort [1B] Info=10262e40 Flags=0 a_Capi_ccc : OpAbort [1F] Info=10262eb8 Flags=0 a_Capi_ccc : OpAbort [2B] Info=10262fa8 Flags=0 a_Dpi_ccc : OpAbort [2B] Info=10262da0 Flags=0 a_IO_ccc : OpAbort [2B] Info=10262e90 Flags=0 If you are opening an existing url like dillo.org it puts out: Nav_open_url: new url='http://www.dillo.org/' a_Capi_ccc : OpStart [2B] Info=10262fd0 Flags=0 a_Dpi_ccc : OpStart [2B] Info=10262f08 Flags=0 a_IO_ccc : OpStart [2B] Info=10262e68 Flags=0 a_Capi_ccc : OpStart [1B] Info=10262ee0 Flags=0 a_Http_ccc : OpStart [1B] Info=10262e90 Flags=0 a_IO_ccc : OpStart [1B] Info=10262f30 Flags=0 Http_must_use_proxy: http://www.dillo.org/ NO Dns_server [0]: www.dillo.org is 85.214.105.140 Connecting to 85.214.105.140 a_IO_ccc : OpSend [1B] Info=10262f30 Flags=0 a_Capi_ccc : OpSend [1F] Info=10262ee0 Flags=0 a_Capi_ccc : OpSend [2B] Info=10262fd0 Flags=0 a_Dpi_ccc : OpSend [2B] Info=10262f08 Flags=0 a_IO_ccc : OpSend [2B] Info=10262e68 Flags=0 http, referer='Referer: http://www.dillo.org/ ' Query: {GE} a_IO_ccc : OpSend [1B] Info=10262f30 Flags=0 and after some seconds: a_IO_ccc : OpEnd [2F] Info=10262e68 Flags=0 a_Dpi_ccc : OpEnd [2F] Info=10262f08 Flags=0 a_Capi_ccc : OpEnd [2F] Info=10262fd0 Flags=0 a_Capi_ccc : OpEnd [1B] Info=10262ee0 Flags=0 a_Http_ccc : OpEnd [1B] Info=10262e90 Flags=0 a_IO_ccc : OpEnd [1B] Info=10262f30 Flags=0 but nothing happens in the dillo window. I would be very happy to get any hint what is going wrong here. Thanks you, Jan

5 21

Dillo on the BLFS wiki
by onepoint＠starurchin.org 06 Aug '14

06 Aug '14

I have updated the Dillo page on the Beyond Linux From Scratch (BLFS) project wiki [1] to version 3.0.4 . Are there any other changes I should make? Perhaps the description of CSS support needs updating - it has come a long way since that part of the page was written. Are there any new configuration files to describe? Please suggest changes and I'll update the page with them. Regards, Jeremy Henty [1]: http://wiki.linuxfromscratch.org/blfs/wiki/dillo3

2 2

abort failed queries
by eocene＠gmx.com 31 Jul '14

31 Jul '14

I wanted to inform the user when a query failed by showing a message and greying out the stop icon instead of letting them wait forever and wonder. Patch attached. Examples: starurchin.org (Connection refused at present, anyway. Fails immediately.) auriga.wearlab.de (no server there, of course. Takes a minute or so.) dillo.asdfgh (leaves the DNS error msgs alone and greys the stop icon.)

1 0

x11 icon name
by eocene＠gmx.com 22 Jul '14

22 Jul '14

On fvwm, there's a pager showing the different windows on the different desktops, and usually the (beginning of the) title of the window is written on the little depiction of the window. But with Dillo, the depiction frequently had no title written on it. And I'd ignored this for a long time. Yesterday, I noticed that it had "O" when I was reading something with a window title of "Dillo: Chapter 7. I/O" and I'm like, "Slashes. It doesn't like slashes..." It seems that fvwm is displaying an "icon name". In Fl_Window::label(), if you don't set an icon name, it takes the label and runs it through fl_filename_name(name) for...some reason, thereby trimming everything up to the final slash. I just tried the attached patch, and the icon name was shown properly. Or maybe it should just be set to "Dillo" and left that way. I don't know whether there are any strong conventions here. Does your window mgr like to use the "icon name" at all?

1 0

diilo in a cpu loop
by higuita7＠yahoo.co.uk 22 Jul '14

22 Jul '14

Hi! I'm using the latest dillo mercurial version and when trying to see this page, dillo uses all cpu and keep using it: http://aventar.eu/2014/07/11/a-historia-do-banco-do-meu-avo/ Thanks for dillo higuita -- Naturally the common people don't want war... but after all it is the leaders of a country who determine the policy, and it is always a simple matter to drag the people along, whether it is a democracy, or a fascist dictatorship, or a parliament, or a communist dictatorship. Voice or no voice, the people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked, and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same in every country. -- Hermann Goering, Nazi and war criminal, 1883-1946

2 3

build fails on CentOS 7
by rdt＠cs.queensu.ca 12 Jul '14

12 Jul '14

: Making all in test make[2]: Entering directory `/home/rdt/src/dillo-3.0.4/test' g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/local/include -I/usr/include/freetype2 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_THREAD_SAFE -D_REENTRANT -g -O2 -Wall -W -Wno-unused-parameter -fno-rtti -fno-exceptions -MT dw_anchors_test.o -MD -MP -MF .deps/dw_anchors_test.Tpo -c -o dw_anchors_test.o dw_anchors_test.cc mv -f .deps/dw_anchors_test.Tpo .deps/dw_anchors_test.Po g++ -I/usr/include/freetype2 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_THREAD_SAFE -D_REENTRANT -g -O2 -Wall -W -Wno-unused-parameter -fno-rtti -fno-exceptions -L/usr/local/lib -o dw-anchors-test dw_anchors_test.o ../dw/libDw-widgets.a ../dw/libDw-fltk.a ../dw/libDw-core.a ../lout/liblout.a -Wl,-z,relro -lfltk /bin/ld: ../dw/libDw-fltk.a(libDw_fltk_a-fltkviewbase.o): undefined reference to symbol 'XCreatePixmap' /bin/ld: note: 'XCreatePixmap' is defined in DSO /lib64/libX11.so.6 so try adding it to the linker command line /lib64/libX11.so.6: could not read symbols: Invalid operation collect2: error: ld returned 1 exit status make[2]: *** [dw-anchors-test] Error 1 make[2]: Leaving directory `/home/rdt/src/dillo-3.0.4/test' Bob T.

2 3

HTTP persistent connections / keep-alive
by eocene＠gmx.com 12 Jul '14

12 Jul '14

I have been experimenting with persistent connections for http, and wanted to see what your thoughts were. This has been working well enough for me: http://flpsed.org/hgweb/eocene_persistent_connections/ Why? To be a good internet citizen, tcp slow-start, etc. Johannes gave it a try and said it performed well. Initially I let FDs stick around even if I didn't immediately have new queries for them. When the server closed it, I'd get EPIPE on the write side and... I think it was ECONNRESET on the read side, send the OpEnd around ccc, and that worked all right and wasn't too messy. But then I wanted to handle the case where a FD sits idle and we try to reuse it and it fails. Sending the notifications around and getting everything back in a state where we could try again with a new connection was looking like it would be very messy. So I trimmed it all down so that, when we have our full reply, we reuse the FD if we already have something queued that can use it, and if not we just close the connection.

1 1

general uri handler
by dennisn＠dennisn.linuxd.org 05 Jul '14

05 Jul '14

How are you guys handling non-builtin uris, like ed2k:, mailto:, magnet:, etc? I hacked a general purpose handler (that calls a shell script) from dpi/hello.c, but surely something this useful should ship with dillo? It seems that this has been a popular request for a long time :P... http://lists.dillo.org/pipermail/dillo-dev/2004-October/002403.html

2 2