From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] tidy debug tree, and a js script
Date: Sun, 30 Aug 2015 05:49:48 -0400 [thread overview]
Message-ID: <20150730054948.eklhad@comcast.net> (raw)
In-Reply-To: <20150830093029.GB17154@toaster.adamthompson.me.uk>
> It turns out what we wanted was tidyNodeGetValue which doesn't do escaping
Well will you look at that!
Like I say, it's a great time to be wrong.
So I guess we're back in the saddle again.
Do keep an eye on us over here, and keep us pointed in the right direction.
Thanks.
Karl Dahlke
next prev parent reply other threads:[~2015-08-30 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 10:04 Karl Dahlke
2015-08-29 13:25 ` Adam Thompson
2015-08-29 14:36 ` Karl Dahlke
2015-08-29 14:58 ` Adam Thompson
2015-08-29 16:05 ` Karl Dahlke
2015-08-30 1:15 ` Kevin Carhart
2015-08-30 8:26 ` Adam Thompson
2015-08-30 9:30 ` Adam Thompson
2015-08-30 9:49 ` Karl Dahlke [this message]
2015-08-30 10:02 ` Adam Thompson
2015-08-30 10:31 ` Karl Dahlke
2015-08-30 11:16 ` Adam Thompson
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=20150730054948.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).