From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] html.c
Date: Fri, 24 Jan 2014 18:09:08 -0800 [thread overview]
Message-ID: <87fvocq0cb.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140024181617.eklhad@comcast.net> (Karl Dahlke's message of "Fri, 24 Jan 2014 18:16:17 -0500")
Karl Dahlke <eklhad@comcast.net> writes:
> thus html.cpp jsdom.cpp jsloc.cpp, through js.h,
> would have a true understanding of js objects including jwin and jdoc.
Yes, this sounds like a plan. I'm working up a patch for the few uses
in buffers.c, against Adam's code, and I'll send that tomorrow. I'll
also convert html.c to html.cpp and do the necessary rooting work.
-- Chris
prev parent reply other threads:[~2014-01-25 2:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 23:16 Karl Dahlke
2014-01-25 2:09 ` Chris Brannon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fvocq0cb.fsf@mushroom.PK5001Z \
--to=chris@the-brannons.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).