| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] | 
What Gnus does when it encounters a new group is determined by the
gnus-subscribe-newsgroup-method variable.
This variable should contain a function. This function will be called with the name of the new group as the only parameter.
Some handy pre-fab functions are:
gnus-subscribe-zombies
gnus-subscribe-randomly
gnus-subscribe-alphabetically
gnus-subscribe-hierarchically
gnus-subscribe-alphabetically is slight.
gnus-subscribe-alphabetically will subscribe new groups in a strictly
alphabetical fashion, while this function will enter groups into its
hierarchy.  So if you want to have the `rec' hierarchy before the
`comp' hierarchy, this function will not mess that configuration
up.  Or something like that.
gnus-subscribe-interactively
gnus-subscribe-killed
gnus-subscribe-topics
subscribe topic
parameter (see section 2.16.5 Topic Parameters).  For instance, a subscribe
topic parameter that looks like
"nnslashdot"  | 
will mean that all groups that match that regex will be subscribed under that topic.
If no topics match the groups, the groups will be subscribed in the top-level topic.
A closely related variable is
gnus-subscribe-hierarchical-interactive.  (That's quite a
mouthful.)  If this variable is non-nil, Gnus will ask you in a
hierarchical fashion whether to subscribe to new groups or not.  Gnus
will ask you for each sub-hierarchy whether you want to descend the
hierarchy or not.
One common mistake is to set the variable a few paragraphs above
(gnus-subscribe-newsgroup-method) to
gnus-subscribe-hierarchical-interactive.  This is an error.  This
will not work.  This is ga-ga.  So don't do it.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |