Re: CUA property not set for multiple functions

[Stefan Monnier]

>> You may argue that if a user binds one of the other commands that may
>> be regarded as a CUA movement command to a single key, CUA will not
>> work for that key -- which is true, but then the user will have to add
>> the necessary CUA property too.  I don't want to "pollude" the sources
>> with properties that are only needed in theory.  But if you know of
>> some specific commands where it may be relevant, pls. tell me and I
>> will consider them case by case.

Can't it be done 99% automatically, rather than with a symbol property?
E.g. use pre-command-hook to remember the buffer-before and tick-before; in
post-command-hook check whether the current buffer is still the same and
whether the tick count has changed and whether the command was bound to
a single key.

IIUC this is only actually used when the key was used with an additional
shift modifier (whereas the binding itself is to a non-shifted key) and it's
only used to mark&activate the region, so false positives are not too
harmful, right?


        Stefan