- Dillo-dev - lists.mailman3.com

[patch]: dpip.c: remove unused static

by onepoint＠starurchin.org

Does anyone know what the static variable DpipTag in dpip.c was used for? It's not used any more. Shall I push this? Regards, Jeremy Henty

Dec. 7, 2010

[patch]: fix the obsolete usage of AC_OUTPUT

by corvid＠lavabit.com

Jeremy wrote: > On Thu, Dec 02, 2010 at 11:28:51AM -0300, Jorge Arellano Cid wrote: > > On Thu, Dec 02, 2010 at 01:08:54PM +0000, Jeremy Henty wrote: > > > > > > Bump? Is this OK? ... > > > > It looks OK to me. Especially after reading the AC_OUTPUT section in > > http://www.gnu.org/software/hello/manual/autoconf/Obsolete-Macros.html#Obso… > > > > I'd say: commit, and let's see whether a hidden issue arises. > > OK, I'll hang on to it over the weekend and then push it if there are > no other comments. I had looked at the docs and it seemed all right to me as well, but of course I'm no autoconf expert either.

Dec. 3, 2010

[patch]: fix the obsolete usage of AC_OUTPUT

by onepoint＠starurchin.org

On Thu, Dec 02, 2010 at 11:28:51AM -0300, Jorge Arellano Cid wrote: > On Thu, Dec 02, 2010 at 01:08:54PM +0000, Jeremy Henty wrote: > > > > Bump? Is this OK? ... > > It looks OK to me. Especially after reading the AC_OUTPUT section in > http://www.gnu.org/software/hello/manual/autoconf/Obsolete-Macros.html#Obso… > > I'd say: commit, and let's see whether a hidden issue arises. OK, I'll hang on to it over the weekend and then push it if there are no other comments. Regards, Jeremy Henty

Dec. 3, 2010

[patch]: fix the obsolete usage of AC_OUTPUT

by jcid＠dillo.org

On Thu, Dec 02, 2010 at 01:08:54PM +0000, Jeremy Henty wrote: > > Bump? Is this OK? Personally I think it's a no-brainer but I didn't > to change the build system in any way without feedback. Please > comment. It looks OK to me. Especially after reading the AC_OUTPUT section in http://www.gnu.org/software/hello/manual/autoconf/Obsolete-Macros.html#Obso… I'd say: commit, and let's see whether a hidden issue arises. > On Sun, Nov 28, 2010 at 05:06:17PM +0000, Jeremy Henty wrote: > > > > While implementing the Lua DPI I saw that configure.in uses AC_OUTPUT > > in an obsolete way. This patch changes it to use the modern calling > > convention. (It also puts each of the generated files on a separate > > line, which makes it much easier to read patches that modify that > > list.) > > > > Regards, > > > > Jeremy Henty > > > # HG changeset patch > > # Parent d21e2c45d0f9a2e1a6bb718132f948d48f619a73 > > configure.in: fix the obsolete usage of AC_OUTPUT. > > > > diff -r d21e2c45d0f9 configure.in > > --- a/configure.in Sun Nov 28 08:07:52 2010 +0000 > > +++ b/configure.in Sun Nov 28 16:52:48 2010 +0000 > > @@ -511,5 +511,18 @@ > > AC_SUBST(LIBICONV_LIBS) > > AC_SUBST(datadir) > > > > -AC_OUTPUT(Makefile dlib/Makefile dpip/Makefile dpid/Makefile dpi/Makefile doc/Makefile dw/Makefile lout/Makefile src/Makefile src/IO/Makefile test/Makefile) > > +AC_CONFIG_FILES([ > > + Makefile > > + dlib/Makefile > > + dpip/Makefile > > + dpid/Makefile > > + dpi/Makefile > > + doc/Makefile > > + dw/Makefile > > + lout/Makefile > > + src/Makefile > > + src/IO/Makefile > > + test/Makefile > > +]) > > > > +AC_OUTPUT > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev > -- Cheers Jorge.-

Dec. 2, 2010

[patch]: fix the obsolete usage of AC_OUTPUT

by onepoint＠starurchin.org

Bump? Is this OK? Personally I think it's a no-brainer but I didn't to change the build system in any way without feedback. Please comment. Regards, Jeremy Henty On Sun, Nov 28, 2010 at 05:06:17PM +0000, Jeremy Henty wrote: > > While implementing the Lua DPI I saw that configure.in uses AC_OUTPUT > in an obsolete way. This patch changes it to use the modern calling > convention. (It also puts each of the generated files on a separate > line, which makes it much easier to read patches that modify that > list.) > > Regards, > > Jeremy Henty > # HG changeset patch > # Parent d21e2c45d0f9a2e1a6bb718132f948d48f619a73 > configure.in: fix the obsolete usage of AC_OUTPUT. > > diff -r d21e2c45d0f9 configure.in > --- a/configure.in Sun Nov 28 08:07:52 2010 +0000 > +++ b/configure.in Sun Nov 28 16:52:48 2010 +0000 > @@ -511,5 +511,18 @@ > AC_SUBST(LIBICONV_LIBS) > AC_SUBST(datadir) > > -AC_OUTPUT(Makefile dlib/Makefile dpip/Makefile dpid/Makefile dpi/Makefile doc/Makefile dw/Makefile lout/Makefile src/Makefile src/IO/Makefile test/Makefile) > +AC_CONFIG_FILES([ > + Makefile > + dlib/Makefile > + dpip/Makefile > + dpid/Makefile > + dpi/Makefile > + doc/Makefile > + dw/Makefile > + lout/Makefile > + src/Makefile > + src/IO/Makefile > + test/Makefile > +]) > > +AC_OUTPUT

Dec. 2, 2010

Dillo needs scripting

by onepoint＠starurchin.org

On Tue, Nov 30, 2010 at 12:21:05PM -0300, Jorge Arellano Cid wrote: > For a few years I've entertained the idea of having lua scripting > in dillo. Not only dpi, but also inside. Looks like dpi > filters/servers are a good start. I think Lua is a good match for Dillo - it's designed to be statically embedded and like Dillo it puts a very high premium on being small and fast. My original motivation was thinking of all the work it take to write eg. a proper fully-featured HTTPS dpi and thinking "it would be *so* much easier to do this in a scripting language instead of C/C++". Regards, Jeremy Henty

Nov. 30, 2010

Dillo needs scripting

by jcid＠dillo.org

On Fri, Nov 26, 2010 at 05:05:26PM +0000, Jeremy Henty wrote: > > I thought it would be fun if I could write a DPI filter as easily as > this: > > #!/usr/lib/dillo/bin/lua-dpi > -- -*- lua -*- > > dpi [[ > Content-type: text/html > > <!DOCTYPE HTML PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN'> > <html> > <head><title>Hello World - Lua DPI</title></head> > <body> > From inside a Dillo DPI, Lua says "Hello World!". > </body> > </html> > ]] > > Well, now I can! > > http://starurchin.org/dillo/dillo_lua_dpi.png > > It's still just a toy at the moment, but I'm pleased with it. Nice! For a few years I've entertained the idea of having lua scripting in dillo. Not only dpi, but also inside. Looks like dpi filters/servers are a good start. -- Cheers Jorge.-

Nov. 30, 2010

[patch]: fix .hgignore

by jcid＠dillo.org

On Sat, Nov 27, 2010 at 09:25:38PM +0100, Johannes Hofmann wrote: > On Sat, Nov 27, 2010 at 05:01:57PM +0000, corvid wrote: > > Jeremy wrote: > > > On Sat, Nov 27, 2010 at 03:28:36PM +0000, corvid wrote: > > > > Back in July, Jeremy wrote: > > > > > corvid wrote: > > > > > > Jeremy wrote: > > > > > > > The problem was that .hgignore contains a line "dillo", which > > > > > > > ignores every file with the string "dillo" anywhere in its > > > > > > > path. Many other lines in .hgignore are similarly > > > > > > > inappropriate. It looks as though these lines were written to > > > > > > > be interpreted as glob-style patterns, but in fact mercurial > > > > > > > interprets every line as a regexp. > > > > > > > > > > > > Looking in http://www.selenic.com/mercurial/hgignore.5.html it > > > > > > seems that specifying "syntax: glob" is also a possibility. > > > > > > > > > > Yes, glob syntax might well be better, but either way the current > > > > > .hgignore is not working as it should and could do with fixing. > > > > > > > > Just noticed this thread while cleaning out old mail, and we should > > > > come to some kind of decision on this. > > > > > > Heh, I was *just* about to bump this discussion by resubmitting my > > > patch! Is there any reason not to push this? Unless people would > > > prefer glob syntax? > > > > My opinion is: Either syntax, as long as it's fixed... > > Also my opinion. +1 -- Cheers Jorge.-

Nov. 29, 2010

OT: freehg.org gone?

by onepoint＠starurchin.org

Not that it affects us, but did anyone notice that freehg.org has gone? I can't Google anything useful, does anyone know more? Regards, Jeremy Henty

Nov. 29, 2010

[patch]: fix the obsolete usage of AC_OUTPUT

by onepoint＠starurchin.org

While implementing the Lua DPI I saw that configure.in uses AC_OUTPUT in an obsolete way. This patch changes it to use the modern calling convention. (It also puts each of the generated files on a separate line, which makes it much easier to read patches that modify that list.) Regards, Jeremy Henty

Nov. 28, 2010