From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] new window assert
Date: Sat, 26 Apr 2014 11:16:12 -0700 [thread overview]
Message-ID: <87iopwufbn.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140426172925.GR23557@toaster.adamthompson.me.uk> (Adam Thompson's message of "Sat, 26 Apr 2014 18:29:25 +0100")
Adam Thompson <arthompson1990@gmail.com> writes:
> Agreed, I've spent much of my life over the last few years looking at
> stackoverflow.com answers.
Yes, it's a really nice site.
Have you ever tried posting to it with edbrowse? I haven't, but I
really should, because I know I'd have a lot to contribute.
Another site I really enjoy reading is reddit.com. Unfortunately, there
are so many visual-only captchas there that it is unusable, unless
you're using something like webvism. So it's another place where I do
not contribute.
-- Chris
next prev parent reply other threads:[~2014-04-26 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 4:04 Karl Dahlke
2014-04-26 17:29 ` Adam Thompson
2014-04-26 18:16 ` Chris Brannon [this message]
2014-04-27 6:17 ` Adam Thompson
2014-04-27 12:41 ` 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=87iopwufbn.fsf@mushroom.PK5001Z \
--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).