From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Subject: [edbrowse-dev] High Hanging Fruit
Date: Tue, 15 May 2018 00:52:31 -0400 [thread overview]
Message-ID: <20180415005231.eklhad@comcast.net> (raw)
In-Reply-To: <20180514213815.cdy42c6sy2ct6jhm@toaster>
[-- Attachment #1: Type: text/plain, Size: 239 bytes --]
I think acid will be a big help.
I went through the first 192 lines, which is just prep, not even acid test 0, and I already found 3 things I was doing wrong, which I have now fixed.
So as time permits I'll move forward.
Karl Dahlke
next prev parent reply other threads:[~2018-05-15 4:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 20:02 Karl Dahlke
2018-05-14 21:38 ` Adam Thompson
2018-05-15 4:52 ` Karl Dahlke [this message]
2018-05-14 23:16 ` Kevin Carhart
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=20180415005231.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=edbrowse-dev@edbrowse.org \
/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).