Re: Flyspell-mode breaks CUA mode

[Stefan Monnier]

>> I think running ispell-check-version (which does various things including
>> running a subprocess) from a post-command-hook is the core of the problem.
> ....
>> (because
>> flyspell's post-command-hook ends up setting deactivate-mark to t).

> Why is it setting deactivate-mark?

Because:
1 - any buffer modification sets deactivate-mark
2 - ispell-check-version puts the output of `ispell -V' in a buffer
3 - as mentioned flyspell's post-command-hook ended up calling
    ispell-check-version


        Stefan