Re: An idea: controlling the order of execution of elisp hook functions

[Eli Zaretskii]

On 10 Dec 2001, Kim F. Storm wrote:

> > Perhaps such a category scheme could simply store, together with the
> > hook, the name of the package that added the hook.  Then other
> > packages could decide whether they need to put their hook before or
> > after the hooks that are already in the list.  A simple extension of
> > add-hook could provide a `before' and an `after' feature.
> 
> Suppose package A knows its hook should come before package B, but B
> doesn't know about A.
> 
> Now, if A's hook is added before B, then you need to store the `before B'
> requirement too, to handle adding B's hook later on.

Most of the packages don't have any requirements about whereabouts of
their hooks.  If they did, the current situation would wimply not
work.  The fact that it does suggests that the interdependencies
between the hooks are largely a non-issue.

Assuming that only a handful of hooks need to be placed before or
after a certain other hook, do you still see a problem?