From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [edbrowse-dev] Threads (fwd)
Date: Mon, 02 Sep 2019 14:53:44 -0400 [thread overview]
Message-ID: <20190802145344.eklhad@comcast.net> (raw)
In-Reply-To: <17349a8a-4eda-3146-1514-568b74c09594@geoffair.info>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
> I can see you prefer separation...
I have no preference; reply any way you wish; and I appreciate all your hard work.
As per make - some of our distributers prefer using make.
You can download virtually any package from any linux distribution, and the instructions tell you to type config, sometimes, and then make.
I can't change how the world works and what the world wants.
If I could, blind people everywhere would be using edbrowse,
because, in my opinion, and it's just my opinion,
pasting a screen reader on a graphical browser is like giving a newly blind pilot a 37,000 foot cane and telling him to go back to work.
We all do the best we can.
I'll have a look at truncate, see where and why it is used, see if there is an alternative.
Please stand by.
Karl Dahlke
next prev parent reply other threads:[~2019-09-02 18:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 2:58 Kevin Carhart
2019-09-01 3:04 ` Karl Dahlke
2019-09-01 18:37 ` Geoff McLane
2019-09-02 2:48 ` Karl Dahlke
2019-09-02 18:38 ` Geoff McLane
2019-09-02 18:53 ` Karl Dahlke [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-28 5:46 Kevin Carhart
2019-08-28 6:25 ` Karl Dahlke
2019-08-29 3:23 ` Kevin Carhart
2019-08-29 19:46 ` Geoff McLane
2019-08-29 21:05 ` Karl Dahlke
2019-08-30 19:23 ` Geoff McLane
2019-08-30 21:26 ` Karl Dahlke
2019-08-30 22:08 ` Karl Dahlke
2019-08-31 19:05 ` Geoff McLane
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=20190802145344.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).