[Pmwiki-users] is "Main" a group, or isn't it?

[Robert P. J. Day]

  i'm a little confused as to how to interpret references to the
group(?) Main.  is Main an actual group, or isn't it?

  initially, i thought it was, since pmwiki came pre-installed with
two default "groups": Main and PmWiki.  that seemed fairly
straightforward.

  but as i was reading about per-group customizations, i got a little
freaked by the following statement:

"For all LocalCustomizations, PmWiki first processes the
local/config.php file, and then looks for a per-page customization
file in the local/ subdirectory to process. If there is no per-page
customization file then PmWiki looks for a per-group customization,
and if that doesn't exist it looks for a per-group customization file
for the group given by the $DefaultGroup (usually "Main")."

  i don't understand that last part -- why would the customization
process consult, as a last resort, the Main group for any
customization?  this suggests that Main is, in fact, *not* an actual
group but some kind of overarching meta-group or something like that
-- more like some kind of abstract group.

  actually, it's more than that -- it's not so much that the
customization process will look for Main customization, as it looks
for customization for whatever group is identified by $DefaultGroup,
which seems just as inappropriate.

  say i happen to want 3 groups in my pmwiki, call them A, B and C.
arbitrarily, i can choose any of them to be my default group, but then
any customzation for that group will potentially affect all of the
remaining groups.  i'm not sure that's such a good idea.

  am i reading this the right way?  wouldn't it make more sense to
have top-level customization done by some kind of abstract, non-group
identifier, like "All" or something, that doesn't correspond to an
actual, physical group?

  thoughts?

rday