From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] parser separation
Date: Sun, 30 Aug 2015 15:25:22 -0400 [thread overview]
Message-ID: <20150730152522.eklhad@comcast.net> (raw)
In-Reply-To: <20150830190618.GC23730@toaster.adamthompson.me.uk>
> one of the things I'd like to do is decouple the parsing logic from js
Yes yes absolutely.
That's what we're goinhg to do.
Karl Dahlke
prev parent reply other threads:[~2015-08-30 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 11:31 Karl Dahlke
2015-08-30 11:43 ` Adam Thompson
2015-08-30 12:21 ` Karl Dahlke
2015-08-30 19:06 ` Adam Thompson
2015-08-30 19:25 ` Karl Dahlke [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=20150730152522.eklhad@comcast.net \
--to=eklhad@comcast.net \
--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).