edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Kevin Carhart <kevin@carhart.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] (something other than) whitespace nodes
Date: Sat, 2 Sep 2017 09:03:20 +0000	[thread overview]
Message-ID: <20170902090320.GB10968@odin> (raw)
In-Reply-To: <alpine.LRH.2.03.1708252108110.27415@carhart.net>

First of all thanks for all the work you've all done on this and appologies for
going silent... again... Hopefully this time I'll keep my computers working at
least long enough to participate in discussions again.

On Fri, Aug 25, 2017 at 09:25:42PM -0700, Kevin Carhart wrote:
> 
> Thanks for pointing this out.  I guess I took something overly literal that
> is not a part of the generic principle they're getting at in the test.
> Clearly node-ifying every '\n' in every web page isn't common or important
> or we would have hit it previously.. I could have keyed in to this fact
> sooner.  Oh well.  I was only in tidy for a short time, and the exploration
> seems useful anyhow.

Tbh it sounds like it wasn't wasted time in that we now understand that this
could be a thing in the future (although it sounds like a strange thing which is
probably why tidy doesn't do it).  I'd also say that the more we know about the
tidy code the better so, as you say, the exploration was probably worth it.
Anyway I agree with safely ignoring the lack of a newline because... who cares
about blank text nodes (which is, I guess, what this would be).  May be we need
this in the future, but I can't imagine why.

Cheers,
Adam.

  reply	other threads:[~2017-09-02  9:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-19 15:38 [Edbrowse-dev] acid[0] Karl Dahlke
2017-08-19 22:53 ` Kevin Carhart
2017-08-19 23:08   ` Karl Dahlke
2017-08-19 23:33     ` Kevin Carhart
2017-08-20  0:00       ` Karl Dahlke
2017-08-20  0:37         ` Kevin Carhart
2017-08-20 14:33           ` Karl Dahlke
2017-08-20 20:00             ` Kevin Carhart
2017-08-20 20:08               ` [Edbrowse-dev] getAttributeNode / setAttributeNode Kevin Carhart
2017-08-20 20:24                 ` Karl Dahlke
2017-08-20 20:56                   ` Kevin Carhart
2017-08-20 21:59                     ` Kevin Carhart
     [not found]                       ` <20170721105041.eklhad@comcast.net>
2017-08-21 19:11                         ` Kevin Carhart
2017-08-21 20:01                           ` Karl Dahlke
2017-08-24  9:54                             ` Kevin Carhart
2017-08-24  9:57                             ` Kevin Carhart
2017-08-25  8:19                             ` Kevin Carhart
2017-08-25 22:09                               ` [Edbrowse-dev] whitespace nodes Kevin Carhart
2017-08-25 22:56                                 ` Karl Dahlke
2017-08-26  4:25                                   ` [Edbrowse-dev] (something other than) " Kevin Carhart
2017-09-02  9:03                                     ` Adam Thompson [this message]
2017-09-02 15:42                                       ` 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=20170902090320.GB10968@odin \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=kevin@carhart.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).