edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev]  segfault in latest Edbrowse
Date: Fri, 05 Feb 2016 08:59:22 -0500	[thread overview]
Message-ID: <20160105085922.eklhad@comcast.net> (raw)
In-Reply-To: <20160204203741.GA6810@122oven.adamthompson.me.uk>

Fixed by last push.

The problem here was me trying to work around the <A><DIV> tidy bug,
illustrated by:
http://www.eklhad.net/div
My tree rearranger worked most of the time, particularly in facebook,
cleaned a lot of things up,
but it found a false positive somewhere in stackoverflow,
fixed a tree that didn't need fixing, thus breaking the tree,
and that led to all the problems.
So I commented out the routine for now,
and stackoverflow works again, and facebook is back to being a little clunky.
In general, if you see

{} farm animals

It could likely mean {farm animals},
and you should click on the empty braces to see.

The moral if there is one is to be wary of trying to work around things
via html preprocessing code or tree postprocessing code.
Unless a bug really derails pages (which has happened in the past),
I should probably exercise patience, because tidy always catches up.

Karl Dahlke

  parent reply	other threads:[~2016-02-05 13:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 20:37 Adam Thompson
2016-02-05  5:28 ` Karl Dahlke
2016-02-05  6:47 ` Chris Brannon
2016-02-05  9:25 ` Chris Brannon
2016-02-05 13:59 ` Karl Dahlke [this message]
2016-02-05 14:21   ` Geoff McLane
2016-02-06 11:57     ` Adam Thompson
2016-02-06 12:03   ` Adam Thompson

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=20160105085922.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).