This is very hard when I really don't know what is most likely to be customized. I wish I was better at writing extensible programs! An rcfile.model sounds fine. (Although, if this gets out of hand a config file in /etc is probably the best solution... except maybe not if we want to sync the RPM spec file with "make install". Arg.) As for rcfile generation at subscription time, what would you base the individual rcfile customizations on? I guess I don't understand the goal.
>BTW, re-organization should take account of the possibility of switching >from shell to perl so that somebody could implement a package for >Windows platforms too. I'm sure it is possible, although not a trivial, due to the heavy reliance on MH. Jeff
