edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@lists.the-brannons.com, baggett@Colorado.EDU
Subject: Re: [Edbrowse-dev] Continuing Amazon issue
Date: Mon, 8 Jan 2018 07:07:56 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1801080654280.6951@debian.pulsar.com> (raw)
In-Reply-To: <20180008025728.eklhad@comcast.net>

Wow! I need some guidance on using db5 here.

First of all, I retrieved amazon.wendy.5 with wget, which turns out to 
be 3.5 mb. I looked at the first few lines and the last few, and saw 
that the db level was already in effect when "e www.amazon.com" was 
issued, so I set mine in the config file.

I started the script program to capture output, then issued

e  www.amazon.com

I admired all the passing lines, waiting for the chatter to quiet down,
but it never did. There seemed to be timers doing their thing
indefinitely, until I lost patience and exited edbrowse with a q.

What am I missing? Is there another way to capture debug output? I can't 
get to the sign-in screen and do my thing there with all the timers 
chattering at me.

Chuck


-- 
Here In Northeast Ohio also, The Moon is Waning Gibbous (55% of Full)
When your only tool is a hammer, everything looks like a nail.
Sent from Bert's iPhone.

  reply	other threads:[~2018-01-08 12:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-07 20:56 Chuck Hallenbeck
2018-01-08  1:18 ` Kevin Carhart
2018-01-08  2:07   ` Karl Dahlke
2018-01-08  4:16     ` Kevin Carhart
2018-01-08  7:55       ` Karl Dahlke
2018-01-08  7:57       ` Karl Dahlke
2018-01-08 12:07         ` Chuck Hallenbeck [this message]
2018-01-08 15:12       ` Karl Dahlke
2018-01-08 15:33         ` 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.DEB.2.21.1801080654280.6951@debian.pulsar.com \
    --to=chuckhallenbeck@gmail.com \
    --cc=baggett@Colorado.EDU \
    --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).