From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (71-38-131-64.ptld.qwest.net [71.38.131.64]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id 922F77890C for ; Sun, 13 Sep 2015 01:14:58 -0700 (PDT) From: Chris Brannon To: Edbrowse-dev@lists.the-brannons.com References: <20150812212213.eklhad@comcast.net> Date: Sun, 13 Sep 2015 01:17:42 -0700 In-Reply-To: <20150812212213.eklhad@comcast.net> (Karl Dahlke's message of "Sat, 12 Sep 2015 21:22:13 -0400") Message-ID: <87h9myu40p.fsf@mushroom.localdomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] tidy script bug workaround X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Sep 2015 08:14:58 -0000 Karl Dahlke writes: > Well if they've been talking about this bug since 2007, > then they might not fix it soon. Yeah, but on the other hand, some of that discussion was from the original tidy project, which has been more-or-less dead for some years now. Tidy 5 is new enough that I'm hopeful. Seems that Kevin has been interacting with their issue tracker and possibly their team; I'm happy to do what I can to help on that front also. > but this one I think people should look at first. > It is ready to push if you say go. I'm giving this a very tentative go. I read through it a couple times. I don't see anything obviously wrong, but yeah, it's tricky. PS. I'm seeing more and more examples of this in the wild, including one on a BBC news site. -- Chris