edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] js abort on db5
Date: Wed, 28 Dec 2016 20:19:32 -0800	[thread overview]
Message-ID: <87a8bfwenf.fsf@the-brannons.com> (raw)
In-Reply-To: <20161128222920.eklhad@comcast.net> (Karl Dahlke's message of "Wed, 28 Dec 2016 22:29:20 -0500")

Karl Dahlke <eklhad@comcast.net> writes:

> If you were running js, with debug 5, and js is done, it's hard to see
> why you would want to march on. You can't even run jdb any more.

My first thought was to make this some sort of toggle command, like
"jsf".  When set, we wouldn't march on at debug >= 5.  But I can't think
of a good reason for having it unset.  Probably best just to crash and
burn here, and not produce all that extraneous debug output.

-- Chris

      parent reply	other threads:[~2016-12-29  4:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29  2:30 Kevin Carhart
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 [this message]

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=87a8bfwenf.fsf@the-brannons.com \
    --to=chris@the-brannons.com \
    --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).