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

[Kai Großjohann]

Luc Teirlinck <address@hidden> writes:

>    (1) The user might have modified the default value before loading
>        crisp.
>
> You mean by making personal changes to cua?  Yes, that would be a
> problem.

I meant that the user might have done this:

(setq cua-movement-commands ...)
(require 'crisp)

Hm.  Oh!  Your suggestion was to use defvar in crisp.  That wouldn't
overwrite the value.

D'oh.
-- 
A preposition is not a good thing to end a sentence with.