From: Harry Putnam <reader@newsguy.com>
Subject: Re: Gnus deja interface
Date: 05 Mar 2000 07:09:35 -0800 [thread overview]
Message-ID: <m2aekdpi6o.fsf@reader.ptw.com> (raw)
In-Reply-To: Bud Rogers's message of "05 Mar 2000 08:47:55 -0600"
Bud Rogers <budr@sirinet.net> writes:
> Harry Putnam <reader@newsguy.com> writes:
>
> > Has something recent happened at Deja.com that is starting to break
> > our Gnus `G w'.
>
> Wow. How long has that been in there?? Another marvelous toy I didn't
> know about.
>
> > With a simple query like: pc-buf
> > I suddenly get:
> >
> > Contacting www.deja.com:80
>
> [...]
>
> > Parsed 100% of 6646...done
> > Lisp nesting exceeds max-lisp-eval-depth
>
> Using the same query I got 'Couldn't request group: No matching articles.'
Are you sure you used the exact same query against dejanews?
pc-buf
Trying here a few more times I still get the nesting error.
> Which I'm not sure I believe, but the connection to deja and the search
> seemed to work OK. At least AFAICT reading the sequence of events as it
> scrolled by in the minibuffer. How did you capture the minibuffer output
> like that?
Capturing the minibuffer output is an ancient yet secret trick known
only to 3 people in the world. So after I tell you, you can expect
the black helicopters in a day or two.
After the messages scroll by, press C-x b *M<SPC> <RET> To see the
*Messages* buffer. Gnus will probably remove the asterisks and
boldify the words they surround so to see what needs to be typed press
C-u g on this message to see the raw message.
Or C-x b <asterisk>M<SPC> <RET> to see
<asterisk>Messages<asterisk> buffer.
next prev parent reply other threads:[~2000-03-05 15:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-05 14:22 Harry Putnam
2000-03-05 14:47 ` Bud Rogers
2000-03-05 15:09 ` Harry Putnam [this message]
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=m2aekdpi6o.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).