From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] version
Date: Sat, 17 Feb 2018 23:45:10 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1802172332290.17556@carhart.net> (raw)
In-Reply-To: <20180117220351.eklhad@comcast.net>
This was a lot of good information in a short time.
Here's some discoveries. Try ucla.edu, uiuc.edu and vmware.com .
I have a 5M file if you want it. But you can make your own easily enough.
I'm a fan of ebrc functions, by the way. All I had to do was assemble
some "b" statements in a function and start capturing. They're great.
On Sat, 17 Feb 2018, Karl Dahlke wrote:
> Things like URL.slice are exactly the kind of things I want to put in *before* a new version.
> Two lines of code that might make some websites work that didn't work before, and really can't break anything.
> I'm hoping you'll find more such fixes in the next week or so.
>
> If you find a bug, or especially a seg fault, then definitely let me know.
> I'm still somewhat uncomfortable about Chuck's bug, because it has not been diagnosed.
> Might be curl's bug, probably is, but it might be mine.
> I might have a workaround for it, but I'm still contemplating that one, and if so, should that be pre or post 3.7.2.
> It's not unusual for me to work around bugs, e.g. a couple in tidy5.
>
> Karl Dahlke
> _______________________________________________
> Edbrowse-dev mailing list
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
>
--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
next prev parent reply other threads:[~2018-02-18 7:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 11:56 Karl Dahlke
2018-02-15 18:48 ` Adam Thompson
2018-02-15 21:04 ` Karl Dahlke
2018-02-16 19:11 ` Adam Thompson
2018-02-18 2:19 ` Karl Dahlke
2018-02-18 2:42 ` Kevin Carhart
2018-02-18 3:03 ` Karl Dahlke
2018-02-18 3:39 ` Kevin Carhart
2018-02-18 7:43 ` Karl Dahlke
2018-02-18 8:17 ` Dominique Martinet
2018-02-18 8:47 ` Dominique Martinet
2018-02-18 8:30 ` Kevin Carhart
2018-02-18 7:45 ` Kevin Carhart [this message]
2018-02-18 8:55 ` Karl Dahlke
2018-02-18 11:29 ` Karl Dahlke
2018-02-18 14:08 ` Karl Dahlke
2018-02-19 1:07 ` [Edbrowse-dev] version / dyndns Kevin Carhart
2018-02-19 3:58 ` [Edbrowse-dev] update on dyndns Kevin Carhart
2018-03-24 16:07 [Edbrowse-dev] version Karl Dahlke
2018-03-25 8:11 ` Kevin Carhart
2018-06-11 15:45 [edbrowse-dev] version 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.1802172332290.17556@carhart.net \
--to=kevin@carhart.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).