edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] much more general plugin system
Date: Fri, 9 Mar 2018 20:40:34 +0000	[thread overview]
Message-ID: <20180309204034.nv3a2ebns7qsrdwv@toaster> (raw)
In-Reply-To: <20180204092017.eklhad@comcast.net>

On Sun, Mar 04, 2018 at 09:20:17AM -0500, Karl Dahlke wrote:
> I think this relates to what Adam was asking about last month.
> I didn't follow at the time, but maybe this is it.
> With the latest, we can key on any protocol, not just the ones edbrowse knows about.
> You can even make up nonsensical protocols for your own purpose.

Yeah that's where I was going, although I didn't quite manage to put together a coherent explanation.  Thanks for implementing this.

  reply	other threads:[~2018-03-09 20:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-04 14:20 Karl Dahlke
2018-03-09 20:40 ` Adam Thompson [this message]
     [not found] ` <20180311133017.5luo5p5u76xah72g@toaster>
2018-03-11 15:13   ` Karl Dahlke

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=20180309204034.nv3a2ebns7qsrdwv@toaster \
    --to=arthompson1990@gmail.com \
    --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).