Hrvoje Niksic wrote:
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.
True, but that doesn't make it a good argument *not* to change the
order. There are more important problems, like starting packages from the init
files, resulting in customizations not being set up when the package is run.
--
Didier Verna, didier(a)lrde.epita.fr,
http://www.lrde.epita.fr/~didier
EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 53 14 59 47
94276 Le Kremlin-BicĂȘtre, France Fax.+33 (1) 44 08 01 99 didier(a)xemacs.org