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

[Kai Großjohann]

Luc Teirlinck <address@hidden> writes:

> Kai Grossjohann wrote:
>
>    It also doesn't work to just frob cua-movement-commands, since
>    adding to a list can only be done after the defvar.
>
> So you defvar it to the same value cua would defvar it to and then add
> the two entries.  What is the need for eval-after-load in this situaton?

(1) The user might have modified the default value before loading
    crisp.

(2) With this strategy, the default value for many variables would be
    copied all around the place.  A nightmare if you ever want to
    change the default value.

Or am I misunderstanding something?
-- 
A preposition is not a good thing to end a sentence with.