From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] jdb
Date: Sat, 21 Nov 2015 14:24:57 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1511211409180.31415@carhart.net> (raw)
In-Reply-To: <20151021094812.eklhad@comcast.net>
Changing to jdb is fine with me.
There have been a couple of other threads such as the js-centric design.
Good discussion - I nodded my head but didn't post.
K
On Sat, 21 Nov 2015, Karl Dahlke wrote:
> Before a version is set, I changed the javascript debug command to jdb.
> I asked about this a month ago and no comment; so here we go.
> I think jdb is more intuitive,
> and inline with the other edbrowse db3 commands.
> It is described briefly in documentation.
>
> 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
prev parent reply other threads:[~2015-11-21 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-21 14:48 Karl Dahlke
2015-11-21 22:24 ` Kevin Carhart [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=alpine.LRH.2.03.1511211409180.31415@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).