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] js stop on error
Date: Thu, 23 Jun 2016 21:21:35 -0400	[thread overview]
Message-ID: <20160523212135.eklhad@comcast.net> (raw)

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

             reply	other threads:[~2016-06-24  1:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24  1:21 Karl Dahlke [this message]
2016-06-24 17:13 ` Kevin Carhart
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=20160523212135.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).