edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] tidy tree
Date: Fri, 28 Aug 2015 15:38:17 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1508281528470.9274@carhart.net> (raw)
In-Reply-To: <874mjjw00k.fsf@mushroom.localdomain>



Hi Chris
No problem.  Echoing the text at a higher db level is a good idea.  I'll 
go add that to db6 right now if I can figure it out swiftly and then send 
it to you.  I did not write very much. 
I grabbed existing work, such as this, so thank you Suman Srinivasan.

http://sumancolumbia.blogspot.com/2006/03/parsing-html-using-tidy-and-tidylib.html

Kevin


On Fri, 28 Aug 2015, Chris Brannon wrote:

> Kevin Carhart <kevin@carhart.net> writes:
>
>> Here is what I have right now.
>>
>> The node name is shown.
>> The number in parentheses is the number of levels of nesting.
>> After each node is each attribute name-value pair.
>> What else?
>
> That's very awesome!  Sorry, I must have missed seeing that you had started
> on this.  The only thing I might add is perhaps a display of the
> contents of text nodes.  Or at least the length of the underlying
> string?  On the other hand, maybe that's a little too much noise?
> Perhaps we could show that on higher debug levels?
>
> -- Chris
>

--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists

  reply	other threads:[~2015-08-28 22:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28  2:55 [Edbrowse-dev] tidy and db5 Kevin Carhart
2015-08-28 21:35 ` [Edbrowse-dev] tidy tree Kevin Carhart
2015-08-28 21:55   ` Chris Brannon
2015-08-28 22:38     ` Kevin Carhart [this message]
2015-08-29  1:45 Kevin Carhart
2015-08-29  2:25 ` Karl Dahlke
2015-08-29  3:04   ` Kevin Carhart

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.1508281528470.9274@carhart.net \
    --to=kevin@carhart.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=chris@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).