Re: self contained nnfolder

[Dan Christensen <jdc+news@uwo.ca>]

prj@po.cwru.edu (Paul Jarc) writes:

> Dan Christensen <jdc+news@uwo.ca> wrote:
> > prj@po.cwru.edu (Paul Jarc) writes:
>>> Now my gnus-server-alist is nil
>> 
>> nil?  Oh, maybe I should remove my nnfolder server from there, and
>> keep it in gnus-secondary-select-methods?  I won't try this until I
>> hear whether it is a stupid idea or not.
>
> It's not a stupid idea, but it really ought to work either way.  So if
> it works one way and not the other, then that means you've got a
> problem somewhere else (either cruft in your configuration, or a Gnus
> bug) that just isn't triggered in one case.

I tried setting gnus-server-alist to nil in my .newsrc.eld, and
leaving my gnus-secondary-select-methods as ((nnfolder "")).
This caused a new error on startup, with Gnus complaining:

gnus-check-server: Wrong type argument: symbolp, (nnfolder "")

So I decided to give up, and set gnus-server-alist to

    (("archive" nnfolder ""))

and manually changed all my groups from server name "" to server
name "archive".  Sure enough, Gnus started fine and I can access
the server buffer again.  But then, I looked at my .newsrc.eld
again, and what did I see but:
  
    (setq gnus-server-alist '(("archive" nnfolder "") 
                              ("" nnfolder "")))

This is how it was when this all started.  So I wasn't the one that
did this crazy naming thing, with one server having two names.
Gnus does it for some bizarre reason.

Thanks for all the help.  If anyone has any other suggestions,
let me know.

Dan

-- 
Dan Christensen
jdc+news@uwo.ca