Ben Wing <ben(a)666.com> writes:
The custom init file is where the custom package writes its options.
This
obviously needs to be a separate file from the standard init file. It should
also be loaded before the init file rather than after, as is usually done
currently, so that the init file can override these options if it
wants to.
Please don't change the order.
Init file can override Custom options although custom is loaded later.
Custom is much smarter than it looks. I can elaborate if you want.