From: Harry Putnam <reader@newsguy.com>
Subject: Gnus deja interface
Date: 05 Mar 2000 06:22:23 -0800 [thread overview]
Message-ID: <m2em9ppkdc.fsf@reader.ptw.com> (raw)
Has something recent happened at Deja.com that is starting to break
our Gnus `G w'.
With a simple query like: pc-buf
I suddenly get:
Contacting www.deja.com:80
Loading url-gw...
Loading url-gw...done
Reading [text/html]... 1k
Retrieval complete.
Mark set
Loading url-file...
Loading url-file...done
Mark set
Loading w3-hot...
Loading w3-hot...done
Unknown URL scheme: nil
Parsed 20% of 6646...
Unknown URL scheme: nil
Parsed 39% of 6646...
Unknown URL scheme: nil
Parsed 56% of 6646...
Parsed 66% of 6646...
Parsed 77% of 6646...
Parsed 88% of 6646...
Parsed 100% of 6646...done
Lisp nesting exceeds max-lisp-eval-depth
Or is gnus stumbling on a specific URL only?
I did get an announcement from Deja.com a few day ago announcing some
changes. Geez I hope its easy to fix...
The query: cylcebuffer ... works as expected
The query ~g gnu.emacs.sources cyclebuffer causes the nesting error
I'm pretty sure I've been using Deja style search operators in the past.
It also seems that any query using "dejanewsold"
Returns this same hit:
1 31-Dec [ 0: ] verdana (My Deja)
That contains:
<html>
<head>
<title>Deja.com: 404 Error</title>
The other selection "alta vista" and "reference.com" return
"Couldn't request group: No matching articles"
On this query: tripwire ... a known subject in many linux and unix groups
However the query: ~g comp.os.linux.security tripwire (against
dejanews) works as expected.
Then again the query: ~g gnu.emacs.sources cyclebuffer.el
Blows up with nesting error again.
There seems no consistency to this.
I haven't cvs'ed for a couple weeks so that isn't the source.
next reply other threads:[~2000-03-05 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-05 14:22 Harry Putnam [this message]
2000-03-05 14:47 ` Bud Rogers
2000-03-05 15:09 ` Harry Putnam
2000-03-05 15:36 ` Bud Rogers
2000-03-05 16:11 ` Bud Rogers
2000-03-05 16:53 ` Harry Putnam
2000-03-07 7:48 ` Steinar Bang
2000-03-07 12:14 ` Bud Rogers
2000-03-07 16:36 ` Alan Shutko
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=m2em9ppkdc.fsf@reader.ptw.com \
--to=reader@newsguy.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).