From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] script tags in scripts
Date: Fri, 11 Sep 2015 14:55:44 -0400 [thread overview]
Message-ID: <20150811145544.eklhad@comcast.net> (raw)
In-Reply-To: <20150911180217.GB29720@toaster.adamthompson.me.uk>
> I think we should continue to move forward with the design
Absolutely, and I am.
I'm working on it as we speak.
And I don't think we'll need to change libraries or go back to a handwritten parser either.
I'm pretty comfortable hitching my wagon to tidy5.
This is the first bug in many tests, and either they'll fix it,
or I'll preprocess the text to get around it:
replace </ in a string with <" + "/
That's kinda gross, and maybe a last resort,
but we're not going to retreat.
This new design is the direction we need to travel, for so many reasons.
Karl Dahlke
next prev parent reply other threads:[~2015-09-11 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 0:17 Tyler Spivey
2015-09-11 1:10 ` Karl Dahlke
2015-09-11 5:28 ` Kevin Carhart
2015-09-11 7:39 ` Adam Thompson
2015-09-11 10:17 ` Karl Dahlke
2015-09-11 18:02 ` Adam Thompson
2015-09-11 18:55 ` Karl Dahlke [this message]
2015-09-11 16:37 ` Chris Brannon
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=20150811145544.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).