Re: org-mode and mode hooks.

[Luc Teirlinck <teirllm@dms.auburn.edu>]

Now that I have taken a closer look at things, it is indeed the case
that although post-command-hook will take care of non-derived major
modes that do not follow conventions (and are not run from timers or
processes) and after-change-major-mode-hook will take care of all
modes that follow the conventions, none of the two will take care of
derived modes that do not follow the conventions.  (Where a derived
mode is defined as a major mode that runs another major mode inside
its body).

I do not know whether there are a lot of derived modes that do not
follow the convention.  The most satisfactory solution would obviously
be to make them all follow the conventions.  If this would be
unrealistic, possibilities include to come up with a better fallback
alternative or to simply revert my change.  If we do the latter, I
could fix the original Buffer Menu problem (and potential future
similar problems with reverting non-file buffers) by making
`auto-revert-buffers' run `global-font-lock-mode-buffers'.  This does
not seem very attractive, because the underlying problem with timers
or processes running modes would remain.  I also do not immediately
understand why find-file-hook could not potentially run too early too.

Sincerely,

Luc.