> turning a mode on. Another possibility could be to recognize mode
> variables and call the respective mode functions with the given values
> if they are encountered.
That would be good. Especially since it would solve the problem where you
can't both specify "text-mode" and "flyspell-mode" at the same time (IIRC
the first mode spec which changes the major mode prevents further mode
specs from being considered, but placing flyspell-mode before text-mode
makes no sense since text-mode turns off flylspell-mode).