edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] how about wrapping style placement in try-catch?
Date: Wed, 27 Sep 2017 20:48:17 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1709272047260.32591@carhart.net> (raw)
In-Reply-To: <20170827064819.eklhad@comcast.net>

>
> I'm thinking about bumping the "execute timer" messages from db3 to db4, because timers can fire repeatedly,

Good idea.  It makes sense.  db3 becomes too hard to read with the timers 
going.

      parent reply	other threads:[~2017-09-28  3:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27  4:01 Kevin Carhart
2017-09-27 10:48 ` Karl Dahlke
2017-09-28  3:45   ` [Edbrowse-dev] amazon Kevin Carhart
2017-09-28  4:58     ` Karl Dahlke
2017-09-28  6:45       ` Kevin Carhart
2017-09-28  3:48   ` 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.1709272047260.32591@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).