From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] nls-edbrowse problem
Date: Thu, 21 May 2015 11:37:06 -0700 [thread overview]
Message-ID: <87bnhdn5f1.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20150421125753.eklhad@comcast.net> (Karl Dahlke's message of "Thu, 21 May 2015 12:57:53 -0400")
Karl Dahlke <eklhad@comcast.net> writes:
> Chris are you an nls user?
No, but Deedra is, and it works fine here, both with executables
compiled from source and the static binaries available from the edbrowse
site. They don't use ftp at all. At times, their site can be
*extremely* sluggish. My guess is that this is what is happening. Try
setting db4 and retrying the download.
Obligatory reminder: if you plan to send debugging output to the list,
always check it for cookies, passwords, and other secrets beforehand.
developers@edbrowse.org is probably the best place to send it, as well,
since this is private.
-- Chris
next prev parent reply other threads:[~2015-05-21 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 16:13 Lawrence Baggett
2015-05-21 16:57 ` Karl Dahlke
2015-05-21 18:37 ` Chris Brannon [this message]
2015-05-21 23:27 ` Chuck Hallenbeck
2015-05-23 16:53 ` 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=87bnhdn5f1.fsf@mushroom.localdomain \
--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).