gnus-level-default-subscribed: documentation or behavior bug?

[Rob Browning <rlb@defaultvalue.org>]

I'd hoped a while back to be able to have gnus-no-server show all my
mail groups without having to manually assign levels.  When I noticed
gnus-level-default subscribed, and read the docs to gnus-no-server, I
thought I had a solution.  With regard to gnus-no-server ther docs
say:

  it will just activate all groups on level 1 and 2.  (You should
  preferably keep no native groups on those two levels.)

So I put (setq gnus-level-default-subscribed 2) in my .emacs, thinking
that would do the trick, and forgot about it, not needing
gnus-no-server right then...

However, recently I've needed to use gnus-no-server, and when I call
it it, none of my mail groups show up.  Looking at the code, this is
because gnus-no-server calls gnus-no-server-1, which doesn't just
activate groups in level 1 or 2 (as the docs indicate), but rather
bases the levels on gnus-level-default-subscribed:

  (defun gnus-no-server-1 (&optional arg slave)
    ...
    (let ((val (or arg (1- gnus-level-default-subscribed))))
      (gnus val t slave)

So am I right in presuming that the docs should probably mention the
interaction with gnus-level-default-subscribed, and if so, then is
there any other way to tell gnus to use a particular level as the
default for all the groups from a particular backend (i.e. my nnml
backend)?

(Also wondering if it'll be easy for me to reset
 gnus-level-default-subscribed back to the default, or if I'll have to
 do some dotfile editing...)

Thanks

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4