From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] js engine strings
Date: Fri, 12 Jun 2015 16:48:55 -0400 [thread overview]
Message-ID: <20150512164855.eklhad@comcast.net> (raw)
In-Reply-To: <20150512164457.eklhad@comcast.net>
> Sorry I've not been as active with development recently,
That's just as well.
I really needed to make these "moving to C" changes,
and fix the aforementioned bug, before you make use of the code.
Otherwise you would have had to do the same work.
Sometimes it pays to procrastinate (a little).
Karl Dahlke
prev parent reply other threads:[~2015-06-12 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 5:22 Karl Dahlke
2015-06-12 20:22 ` Adam Thompson
2015-06-12 20:44 ` Karl Dahlke
2015-06-12 20:48 ` 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=20150512164855.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).