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]   tidy debug tree, and a js script
Date: Sat, 29 Aug 2015 12:05:50 -0400	[thread overview]
Message-ID: <20150729120550.eklhad@comcast.net> (raw)
In-Reply-To: <20150829145820.GE31434@toaster.adamthompson.me.uk>

> If we want to print tidy warnings for local files fair enough,
> but lets make it a user's choice,

Actually I'm kinda stupid here.
I built these mashinations for local files or remote files,
and exceptions through some mechanism, filename or config options etc,
but really all I need to do is print the tidy errors at debugLevel 3 or above.
None of our users are going to want to see them,
except a rare few who write their own html,
and they can get along with db3 to check their sourcefiles.
So that's what I should do, but still not what I'm worried about.

> I wonder if it's just a printing thing or something.

Oh I hope it is, but I fear it's not.
(This would be a great time for me to be wrong.)
We aren't passing the contents of script.text to the js engine yet,
but some day we will, when tidy replaces all my software,
and on that day we will be passing

if(3 &lt; 4)

instead of

if(3 < 4)

At least that's how it appears.

Karl Dahlke

  reply	other threads:[~2015-08-29 16:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-29 10:04 Karl Dahlke
2015-08-29 13:25 ` Adam Thompson
2015-08-29 14:36   ` Karl Dahlke
2015-08-29 14:58     ` Adam Thompson
2015-08-29 16:05       ` Karl Dahlke [this message]
2015-08-30  1:15         ` Kevin Carhart
2015-08-30  8:26         ` Adam Thompson
2015-08-30  9:30           ` Adam Thompson
2015-08-30  9:49             ` Karl Dahlke
2015-08-30 10:02               ` Adam Thompson
2015-08-30 10:31                 ` Karl Dahlke
2015-08-30 11:16                   ` 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=20150729120550.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).