From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Interwindow Communication
Date: Wed, 26 Jul 2017 02:09:38 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1707260134160.7041@carhart.net> (raw)
In-Reply-To: <20170626025744.eklhad@comcast.net>
Thank you, Karl. That's exciting. I will be doing more edbrowse after I
publish and release the thing I've been leading up to for 8 months. (It
has to do with quickly deploying an internet map to augment activism.
Mentioning this for the benefit of anyone reading-- I've told Karl about
it!)
That's my excuse but the end is approaching. Heavy editing for the past
week and a half. Moving sections of documentation around, trying code,
dealing with git, banging my head. It really is the heavy period at the
end of writing & editing something, where you are exhilarated that you are
actually going to finish.
It is great that duktape has been a catalyst for all of the recent
improvements. I look forward to digging in to more edbrowse soon.
Kevin
next prev parent reply other threads:[~2017-07-26 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 6:57 Karl Dahlke
2017-07-26 9:09 ` Kevin Carhart [this message]
2017-07-26 10:09 ` Chuck Hallenbeck
2017-07-26 22:56 ` Kevin Carhart
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=alpine.LRH.2.03.1707260134160.7041@carhart.net \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/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).