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

[Richard Stallman]

    Maybe some wording could be added to talk about efficiency.  For
    example, crisp.el adds two entries to cua-movement-commands.  It does
    not make sense for crisp to require cua, as many crisp users probably
    don't want to use cua.  It also doesn't work to just frob
    cua-movement-commands, since adding to a list can only be done after
    the defvar.

The usual way to handle this is with hooks.  Does cua mode have
a cua-mode-hook?