In message <199402081734.AA11812@aw101.iasl.ca.boeing.com>, "Vincent D. Skahan"
> (John P. Rouillard writes:)
> > > Questions:
> > > - what the heck are newconfig, writeconfig, etc ?
> > Oops, I thought that was in the README.CONFIG. The following commands
> > have been added to majordomo:
> [...nice docs omitted...]
I will probably put that into majordomo.8.
> > > I guess the real question is 'ok - you added all this cool new
> > > functionality - now how to I configure majordomo to use it ?'
> > Config files will be created as needed for any list that is without
> > one. If you run a "lists" command against majordomo, it will
> > automatically create config files for all of the lists, but a request
> > for the config file should do the same albeit for that one list.
> pretty cool. that works nicely and the comments in the newly created
> config file look great (as long as when the new release comes out,
> all the possible options are in there...)
If the list maintainer sends a writeconfig command, all of the
possible options from a new release will be there. It isn't done
The joke is that the "comments" keyword wasn't there originally,
actually the multi-line values weren't there either. I was saving all
of my rcs comments etc right in the config file by protecting them
with a #. Using writeconfig destroys these comments.
I think that the next iteration of the config code (majordomo 2.1
maybe) I'll add incremental updating, and I will always use
"writeconfig" before a config file is retrieved. This will provide
automatic updating of all possible options as you want.
Special Projects Volunteer University of Massachusetts at Boston
email@example.com (preferred) Boston, MA, (617) 287-6480
My employers don't acknowledge my existence much less my opinions.