Re: Transient Mark Mode on by default

[Kim F. Storm]

Chong Yidong <address@hidden> writes:

> Furthermore, making shift-selection a 1st class feature isn't too
> difficult, as I've previously shown.  It also has the advantage of
> integrating with and complementing mouse-selection (e.g., you can select
> a region with the mouse, then extend it with shift-selection).

I've also suggested ways to make shift-selection a 1st class feature
based on the CUA approach - by moving part of the stuff that is currently
in the pre-/post-command-hooks into the command loop, and only call the
(modified) CUA-functions when certain conditions are true.

It seems that Richard is in favour of a scheme which supports both ^ in
the interactive spec and a command property (for external packages),
but IMHO, this is overkill -- 

If we name the property something like shift-select, then the help
system can easily tell people that "applying the Shift modifier to
this command will start or extend the active region".  

I actually think this is much easier to accomplish than having to add
that text explicitly to the doc string of each command which has ^ in
the interactive spec.

So no matter what the arguments for "cleanliness" are, I think the
property approach is simpler, better - and has already proven to work
just fine for MANY years!

-- 
Kim F. Storm <address@hidden> http://www.cua.dk