Comment 6 for bug 744001

So I got the customization of basic pcrisis variables working in such
a way as to give me what I was originally looking for (In fact it just
did some nice work on this email!)

Like you said, after you get past the initial "what the hell is this
and why is it done that way?", it actually ends up making some good
sense.

I do agree that the docs could use a couple of full examples (they
seem rather piece-wise at present) for the most common uses, with some
caveats for the headers to use. I think the biggest thing is to have a
better tie in to the main VM documentation, which is the first place a
user would think to look. There is only a brief mention in the Preface
to Add-ons, but if this package is the way to go, then the docs should
reference it in more useful places like the "composing mail" sections,
or even have a section on profiles directing the user toward specific
sections of the pcrisis manual.

Also, the customize interface is not as good as it could be. For
instance the vmpc-conditions has no type when it should be customized
as a repeat list. I'm also not sure why the customize stuff (and
everything else) is vmpc and not vm-pcrisis, which makes the
customization not as obvious.

So, in conclusion, perhaps some extra setup recipes, a more obvious
name and a place in the vm-docs that say these things can be attained
by putting (require 'vm-pcrisis) in your vm/emacs startup file would
make this an even more powerful addition to vm.

Cheers,
-Arik