Re: eval-after-load as a macro (and eval-next-after-load)

[Miles Bader]

Richard Stallman <address@hidden> writes:
> It could be useful to clean up the way Custom handles hooks.  For
> instance, if Custom sees elements in the hook that it did not put
> there, it could automatically divide the elements into two parts:
> those specified thru Custom, and those specified outside Custom.
> The user, in Custom, would edit only the former.

This sounds good; but I think if it does this, it should also at least
display the `non-custom' hooks in some way, so that the user can see
the whole value.

-Miles
-- 
`To alcohol!  The cause of, and solution to,
 all of life's problems' --Homer J. Simpson