From: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
To: Edbrowse Development <edbrowse-dev@lists.the-brannons.com>
Subject: [Edbrowse-dev] Edbrowse availability somewhat larger.
Date: Fri, 10 Mar 2017 10:33:00 -0500 [thread overview]
Message-ID: <20170310153300.olwo4vfdgujgf7tg@debian.hallenbeck.net> (raw)
I recently subscribed to a shell acount at www.panix.com, and asked
them if edbrowse was available to their user community. They looked it
up on wikipedia, then found www.edbrowse.org, and offered to install
it. A day or two later version 3.6.2 was available. They told me where
their certfile was, and the usersguide.html, and so when I'm there,
it's just like I never left home.
Thought you might like to know that.
Chuck
--
Willoughby Ohio
Temperature 32°F
Conditions Overcast
The Moon is Waxing Gibbous (96% of Full)
next reply other threads:[~2017-03-10 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 15:33 Chuck Hallenbeck [this message]
2017-03-10 17:35 ` Karl Dahlke
2017-03-18 11:13 ` Adam Thompson
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=20170310153300.olwo4vfdgujgf7tg@debian.hallenbeck.net \
--to=chuckhallenbeck@gmail.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).