Re: "Trying to require a method that doesn't exist"

[Harry Putnam <reader@newsguy.com>]

Simon Josefsson <jas@pdc.kth.se> writes:

> Harry Putnam <reader@newsguy.com> writes:
> 
> > Your clues led me to find an improper entry in .newsrc.eld in the
> > section that holds the Group Information.  Begins with:
> > "(setq gnus-newsrc-alist ......"
> > 
> > One of the nnml group entries looks like this:
> > ("nnml:mail.Barb" 3 ((1 . 1)) ((reply 1)) "nnml:")
> > 
> > Where as others have the proper form like so:
> > ("nnml:mail.misc" 3 ((1 . 53) (57 . 57)) ((reply 53)) (nnml ""))
> > 
> > Notice the last part with "nnml" is formatted differently.
> 
> Since 0.52 pGnus tries to shorten select methods to a virtual server
> name if the method is native or secondary -- this lets you change your
> server variables in ~/.gnus without having to edit your ~/.newsrc.
> 
> That is, "nnml:" is really a valid method field in your ~/.newsrc.
> 
> I think that you no longer have `(nnml "")' in
> `gnus-secondary-select-methods', is that true?
> 
> If this is the case, I think the error message is valid and you should
> let Gnus know about a nnml-backend named "" and things should work (by
> adding `(nnml "")' to `gnus-secondary-select-methods' or something to
> that effect).

It may well be that you are on the right track, but the secondary and
primary select methods have remained unchanged for months.


grep "select" .gnus:
;   (setq gnus-select-method '(nntp "enews.newsguy.com"))
(setq gnus-secondary-select-methods '((nnml "")))

I'm just using the env settings for nntp server selection, hence the
comment.

As mentioned previously, each time the problem has come up (completely
blocking use of gnus) it has involved a group where group params have
been set.  Leading me to think it may be caused by my entering some
sloppy lisp in the group params.  The problem has been, how to get to
the group params with gnus not functioning.  I'm beginning to see a
little better how .newsrc.eld works, and at least know what to look
for, but still haven't been able to tell what caused the problem.  If
it comes up again, have you an idea how to better track the source of
the problem?


-- 
Harry Putnam <reader@newsguy.com>
Running Redhat Linux 5.1

.