December 2010 - Dillo-dev - lists.mailman3.com

Yong Li wants to stay in touch on LinkedIn

by sdliyong＠gmail.com

LinkedIn ------------ I'd like to add you to my professional network on LinkedIn. - Yong Li Yong Li platform software developer at Hewlett-Packard China Confirm that you know Yong Li https://www.linkedin.com/e/m1sm8i-ghnbkyy3-6p/isd/2018522004/2K69vPKA/ -- (c) 2010, LinkedIn Corporation

Dec. 13, 2010

[patch]: CSS parser cleanup

by onepoint＠starurchin.org

Just some small cleanup and refactoring of the CSS parser code. Any reason not to push these? Regards, Jeremy Henty

Dec. 13, 2010

[henry@compdata.org: Dillo 2.2 NetBSD macppc StrawBerry iMac 333]

by onepoint＠starurchin.org

On Fri, Dec 10, 2010 at 06:13:25PM -0300, Jorge Arellano Cid wrote: > FYI, > > -- > Cheers > Jorge.- > Just compiled and installed Dillo on an Apple Strawberry iMac 333. > Platform: NetBSD 5.1 macppc That's cool! Is there a list of platforms that Dillo is known to run on? I looked around the web site but couldn't find any such thing. Regards, Jeremy Henty

Dec. 13, 2010

[henry@compdata.org: Dillo 2.2 NetBSD macppc StrawBerry iMac 333]

by jcid＠dillo.org

FYI, -- Cheers Jorge.-

Dec. 10, 2010

[patch]: dpip.c: remove unused static

by onepoint＠starurchin.org

On Tue, Dec 07, 2010 at 01:24:27PM -0300, Jorge Arellano Cid wrote: > On Tue, Dec 07, 2010 at 03:30:20PM +0000, corvid wrote: > > Jeremy wrote: > > > Does anyone know what the static variable DpipTag in dpip.c was used > > > for? It's not used any more. Shall I push this? > > > > It appears to have been introduced in revision 1385, and I don't > > see it being used for anything even then. > > Most probably me, experimenting with the protocol making a > difference between a dpip tag and raw data. > > Currently raw data is escaped within dpip tags so it's safe to > remove. Done. Regards, Jeremy Henty

Dec. 7, 2010

[patch]: dpip.c: remove unused static

by jcid＠dillo.org

On Tue, Dec 07, 2010 at 03:30:20PM +0000, corvid wrote: > Jeremy wrote: > > Does anyone know what the static variable DpipTag in dpip.c was used > > for? It's not used any more. Shall I push this? > > It appears to have been introduced in revision 1385, and I don't > see it being used for anything even then. Most probably me, experimenting with the protocol making a difference between a dpip tag and raw data. Currently raw data is escaped within dpip tags so it's safe to remove. -- Cheers Jorge.-

Dec. 7, 2010

[patch]: dpip.c: remove unused static

by corvid＠lavabit.com

Jeremy wrote: > Does anyone know what the static variable DpipTag in dpip.c was used > for? It's not used any more. Shall I push this? It appears to have been introduced in revision 1385, and I don't see it being used for anything even then.

Dec. 7, 2010

[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