My last attempt was hosed because I put a dot on a line by its self. Oops.
>>>>> "KPB" == Kendall P Bullen <firstname.lastname@example.org> writes:
KPB> Well, of course, it would take some mod's. to Majordomo to allow
KPB> people to edit it remotely, much like the .config, .info, and .intro
KPB> are edited remotely. ;-) It's not much of a stretch. . . .
Actually, it is quite a stretch if you consider the internals and the
coding that would be required to make it work. I'm speaking in the context
of Majordomo 2 here, because I don't see much point in trying to hack
anything into 1.9x. config is gone, replaced by a simpler mechanism that
lets you set one variable at a time (or all of them, like the old command,
or various groups of them). info and intro are replaced by a more general
put mechanism. Syntax checking doesn't happen on text files uploaded to
If you allow an include file syntax, you should do it for every variable.
That's a nightmare, _especially_ in the context of the new system where the
on-disk config files are _not parsed_. They're saved as Perl code (because
it's very quick to load).
If you want a global set of taboo headers, why not just use the global
taboo headers? That is, after all, why they're there.