From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] patch remarks
Date: Thu, 30 Jun 2016 15:58:02 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1606301504480.4266@carhart.net> (raw)
In-Reply-To: <20160530120010.eklhad@comcast.net>
> Well seems reasonable enough so I pushed it,
> plus the substr correction you mentioned.
Thanks Karl!
> 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 know. I agree... it might break some pages that used to work, so it
probably should get uncommented again right away.
It's like a working demo, which is now there for posterity in version
control with a unique hash and timestamp, so it will be downloadable even
when we supercede it with more commits. Maybe another way
of accomplishing this would have been to fork the edbrowse code so that it
is sitting under kcarhart instead of CMB, commit the bundle of changes and
say "would you please compile this in a side folder marked 'experiment'
and try it out? If I do these couple of weird things that are way out on
a limb, as well as these other ten bits of implementation that I can
justify, we can get this whole round trip where several moving parts of
the program work together and a potentially common page behavior works
which doesn't otherwise." It's food for thought, in the form of a
compileable codebase rather than just describing. It kind of plays on the
lovely fact that edbrowse is so light, you can copy around the entire
thing just to illustrate a point, and it doesn't take prohibitive time to
compile or download.
Kevin
next prev parent reply other threads:[~2016-06-30 22:56 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
2016-06-30 22:58 ` Kevin Carhart [this message]
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=alpine.LRH.2.03.1606301504480.4266@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).