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

[Luc Teirlinck]

   (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.

   (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.

Yes that would be a problem too.

   Or am I misunderstanding something?

No, that was just a very bad idea of mine.  I just responded too
quickly, I guess.

Sincerely,

Luc.