Re: 2 things

[jdc@chow.mat.jhu.edu (Dan Christensen)]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> jdchrist@math.mit.edu (Dan Christensen) writes:
> 
> > I still don't see why `gnus-no-server' needs to open each of my
> > nnfolder groups while `gnus' doesn't.
> 
> In addition to not connecting to the server, `gnus-no-server' starts
> up Gnus at a specific level.  Only the groups at or below that level
> will be activated, and Gnus does that activation with
> `nn*-request-group'.  For nnfolder, that means reading in the folder
> and counting articles.

Ahh, I see.  It seems to me that it would be better have
`gnus-no-server' behave exactly like `gnus' except that the server is
not contacted.  The start-up level is an orthogonal issue, and one can
always do `C-u 2 gnus-no-server' if one wants.

Of course, I should be able to obtain the behaviour I want by doing
(gnus nil t), right?  The nil indicates no startup level, and the t
means that gnus shouldn't connect to the server.  However, when you
do this, gnus *does* connect to the server.  Two places where this
happens are indicated below by <------- in the right margin:

(defun gnus-setup-news (&optional rawfile level dont-connect)
  "Setup news information.
If RAWFILE is non-nil, the .newsrc file will also be read.
If LEVEL is non-nil, the news will be set up at level LEVEL."

.......

    ;; Read the active file and create `gnus-active-hashtb'.
    ;; If `gnus-read-active-file' is nil, then we just create an empty
    ;; hash table.  The partial filling out of the hash table will be
    ;; done in `gnus-get-unread-articles'.
    (and gnus-read-active-file
	 (not level)
	 (gnus-read-active-file))                              <------

.......

    ;; Find new newsgroups and treat them.
    (when (and init gnus-check-new-newsgroups (not level) 
	       (gnus-check-server gnus-select-method)          <------
	       (not gnus-slave))
      (gnus-find-new-newsgroups))

.......

    ;; Find the number of unread articles in each non-dead group.
    (let ((gnus-read-active-file (and (not level) gnus-read-active-file)))
      (gnus-get-unread-articles level))

    (when (and init gnus-check-bogus-newsgroups
	       gnus-read-active-file (not level)
	       (gnus-server-opened gnus-select-method))
      (gnus-check-bogus-newsgroups))))

I don't think we simply want to add (not dont-connect) to the and's
above, because we would like our secondary servers to check for new
news, for example.  Maybe dont-connect should get passed along to
gnus-read-active-file, which would use its value in the appropriate way?

Dan

-- 
Dan Christensen
jdc@math.jhu.edu