From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] js abort on db5
Date: Wed, 28 Dec 2016 18:30:11 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1612281817310.31868@carhart.net> (raw)
What do yall think of the idea of making the js abort on db5 even more
violent than it is already? Could we add exit(0) and quit altogether?
Or perhaps not on db5, but could I define this on a large unused db
level such as db999 or just 1+ the highest that we have currently?
Example: I made a mistake in startwindow which was illegal within js
but didn't make compilation fail. I had db5 on. The "js abort due
to error while debugging" appears, but it is followed by hundreds
more lines of tidy and other output. Might take a little time to
understand what happened, and the edbrowse session is shot because
javascript is now disabled so there was no point in continuing with
non-JS.
thanks
Kevin
next reply other threads:[~2016-12-29 2:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 2:30 Kevin Carhart [this message]
2016-12-29 3:29 ` Karl Dahlke
2016-12-29 3:32 ` Kevin Carhart
2017-01-12 18:38 ` Adam Thompson
2017-01-12 18:56 ` Karl Dahlke
2016-12-29 4:19 ` Chris Brannon
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.1612281817310.31868@carhart.net \
--to=kevin@carhart.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).