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]  Error Legs
Date: Sun, 09 Feb 2014 09:18:46 -0500	[thread overview]
Message-ID: <20140109091846.eklhad@comcast.net> (raw)

> I'd still prefer it if it just killed the offending context as well

I agree, and I might be the one to work on this -
but that would be one of those major changes that I think we said we would
wait on until our work was stable.
I keep coming back round to the fact that if we can't get this to work
with moz js 24 libraries as distributed, then edbrowse is dead anyways,
except perhaps on our three machines.
If it can't be distributed then I don't know how much time I should spend on it.
I'm not trying to be Debbie Downer, just practical.
We should be doing what we can to get it to function in the debian world.
If that is both in process and/or on hold,
or if one of you is taking that on, then I could work on error legs in parallel,
and would be willing to do that, as it is a systemic change throughout.
I just keep looking up and seeing the sword of damocles overhead.

Karl Dahlke

             reply	other threads:[~2014-02-09 14:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-09 14:18 Karl Dahlke [this message]
2014-02-09 15:13 ` Adam Thompson
  -- strict thread matches above, loose matches on Subject: below --
2014-02-09 14:48 Karl Dahlke
2014-02-09 15:21 ` Adam Thompson
2014-02-07 20:06 Karl Dahlke
2014-02-07 19:37 Karl Dahlke
2014-02-07 19:55 ` Chris Brannon
2014-02-07 17:57 Karl Dahlke
2014-02-07 18:23 ` Chris Brannon
2014-02-09 10:45   ` Adam Thompson
2014-02-09 11:10     ` Adam Thompson
2014-02-07 14:01 Karl Dahlke
2014-02-07 15:05 ` 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=20140109091846.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).