>> Ken, would it be a bad idea to call context_save() in
>> nmh_version_changed() if the Version context is replaced?
>That's probably the same as asking if no code fiddles with context in
>temporary ways knowing *it's* not going to save it later?
Generally when the context is going to be fiddled with, it's done
after program initialization has taken place and the program in question
is actually DOING things. The issue here is nmh_version_changed() is
being called in nmh_init(), so if the program exits early then it won't
call context_save() in the normal course of things.