Path: utzoo!mnetor!uunet!husc6!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!MAHENDO.JPL.NASA.GOV!earle
From: earle@MAHENDO.JPL.NASA.GOV (Greg Earle)
Newsgroups: comp.emacs
Subject: Problem with Matt Wiener's Gnews 1.1
Message-ID: <8803091214.AA04452@mahendo.Jpl.Nasa.Gov>
Date: 9 Mar 88 12:14:38 GMT
Sender: daemon@eddie.MIT.EDU
Lines: 36

This probably isn't the appropriate place, but since Gnews runs under Emacs,
and Matt isn't around, oh well ...

Has anyone run Gnews 1.1 yet?  I'm having a lot of problems with getting 
errors while doing a re-search-forward looking for a particular NNTP result
code.  To be specific, Gnews is suffering from a rash of
	Search failed: "^222.*$"
(in gnews.el) messages in each newsgroup.  A sample debugger backtrace shows:
	group-get ("alt.config" nil nil)
	(if ...)
	(cond ...)
	(if ...)
	(cond ...)
	(catch ...)
	article-get (79 nil)
	(if ...)
	(if ...)
	(let ...)
	(save-excursion ...)
	(goto-char 1)
	re-search-forward ("^222.*$")

What is bizarre is that I don't know how this can happen.  Before the
save-excursion, an (nntp-exec nil nil "body" number) is performed.  The
first line of the returned text from a (successful) NNTP BODY command is always

	222  (article #)  <nnn@foo.UUCP>  Article retrieved; body follows.

Since the code switches to the first character in the buffer [ (goto-char 1) ]
I can't understand how the regexp forward search can possibly fail!
Sometimes it works, a lot of the time it doesn't.

I'd like to try using `gnews' more often, but this problem is stiffling my
attempts to switch over.  Everything else looks pretty good so far, but
this problem is ruining everything - and it looks like there's no logical
reason for it to be happenning.