From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] js stop on error
Date: Fri, 24 Jun 2016 10:13:13 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1606241005210.22113@carhart.net> (raw)
In-Reply-To: <20160523212135.eklhad@comcast.net>
This would be nice to have. Once you are echoing the JS code, there is so
much output that it is probably good just to take it to the first error.
On Thu, 23 Jun 2016, Karl Dahlke wrote:
> Perhaps js should stop, for that session,
> if a js error occurs and debug >= 5.
> This speaks to Kevin's point that you want to focus on the first js error,
> not the zillionth, and that's what you're doing when at db5 or above.
> This has no effect on our users, who do not debug.
> We can do whatever we want in this area.
>
> Karl Dahlke
> _______________________________________________
> Edbrowse-dev mailing list
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
>
--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
next prev parent reply other threads:[~2016-06-24 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 1:21 Karl Dahlke
2016-06-24 17:13 ` Kevin Carhart [this message]
2016-06-25 5:52 ` 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=alpine.LRH.2.03.1606241005210.22113@carhart.net \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.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).