From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] patch remarks
Date: Thu, 30 Jun 2016 12:00:10 -0400 [thread overview]
Message-ID: <20160530120010.eklhad@comcast.net> (raw)
In-Reply-To: <20160529212929.kevin@carhart.net >
Well seems reasonable enough so I pushed it,
plus the substr correction you mentioned.
Commenting out iframe makes me a little nervous,
it fixes some pages that crashed but mightit also break some pages
that use to work??
I don't understand the new Event call, I guess it works,
but Event isn't a class it's a function, and has no return,
so what is happening with
tempEvent = new Event;
What is assigned to tempEvent?
Karl Dahlke
next prev parent reply other threads:[~2016-06-30 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 4:29 Kevin Carhart
2016-06-30 16:00 ` Karl Dahlke [this message]
2016-06-30 22:58 ` Kevin Carhart
2016-06-30 23:02 ` Karl Dahlke
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=20160530120010.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).