From: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@lists.the-brannons.com
Subject: Re: [edbrowse-dev] fastmail
Date: Thu, 19 Jul 2018 10:03:39 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.21.99.1807190959580.397@workshop> (raw)
In-Reply-To: <20180619092730.eklhad@comcast.net>
> Well we need to figure out why that section of code does not appear, but in the meantime, try this: unbrowse, remove the word disabled, browse, and go.
I did that, but it was no good. However, when I unbrowsed again to
examine that area, the word Disabled" was replaced with a request to
supply the verification code.
Chuck
--
Here too, In Northeast Ohio, The Moon is Waxing Crescent (47% of Full)
If you don't stand for something, you will fall for anything.
Sent from Ignacio's stolen iPhone.
next prev parent reply other threads:[~2018-07-19 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 10:06 Erwin
2018-07-19 13:27 ` Karl Dahlke
2018-07-19 14:03 ` Chuck Hallenbeck [this message]
2018-07-19 15:52 Erwin
2018-07-20 14:48 ` Karl Dahlke
2018-07-20 15:58 ` Chuck Hallenbeck
2018-07-20 23:44 ` Dominique Martinet
2018-07-21 0:39 ` Chuck Hallenbeck
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=alpine.LNX.2.21.99.1807190959580.397@workshop \
--to=chuckhallenbeck@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).