Keep region active after command

Keep region active after command

[Fabian Ezequiel Gallina]

What would be the best way to keep the region active after a command?

What I'm willing to do is to keep the region active after
python-indent-shift-left and python-indent-shift-right are called.


Regards,
-- 
Fabián E. Gallina
http://www.from-the-cloud.com

Re: Keep region active after command

[Stefan Monnier]

> What would be the best way to keep the region active after a command?
> What I'm willing to do is to keep the region active after
> python-indent-shift-left and python-indent-shift-right are called.

The region is deactivated if `deactivate-mark' is non-nil at the end of
the command and this variable is set by buffer-modifying functions, so
let-binding deactivate-mark around those functions (or around the whole
command's body) is usually the way to do it.


        Stefan

Re: Keep region active after command

[Lennart Borgman]

On Sat, Feb 19, 2011 at 10:19 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> What would be the best way to keep the region active after a command?
>> What I'm willing to do is to keep the region active after
>> python-indent-shift-left and python-indent-shift-right are called.
>
> The region is deactivated if `deactivate-mark' is non-nil at the end of
> the command and this variable is set by buffer-modifying functions, so
> let-binding deactivate-mark around those functions (or around the whole
> command's body) is usually the way to do it.


Wouldn't it be good to have a general command like
dont-deactivate-mark-after-next-command?

Re: Keep region active after command

[Chong Yidong]

Lennart Borgman <lennart.borgman@gmail.com> writes:

> Wouldn't it be good to have a general command like
> dont-deactivate-mark-after-next-command?

No.  Having a function that just sets a variable to nil is silly.

Re: Keep region active after command

[Lennart Borgman]

On Sat, Feb 19, 2011 at 11:26 PM, Chong Yidong <cyd@stupidchicken.com> wrote:
> Lennart Borgman <lennart.borgman@gmail.com> writes:
>
>> Wouldn't it be good to have a general command like
>> dont-deactivate-mark-after-next-command?
>
> No.  Having a function that just sets a variable to nil is silly.

?? Please give an argument!

Re: Keep region active after command

[Miles Bader]

Lennart Borgman <lennart.borgman@gmail.com> writes:
>> No.  Having a function that just sets a variable to nil is silly.
>
> ?? Please give an argument!

Because the user may as well just write (setq foo nil)...

If "foo" were obscure/weird, then maybe a set-to-nil function with a
clearer name could be useful useful, but in this case the variable's
meaning is quite clear.

-miles

-- 
Love is the difficult realization that something other than oneself is real.
[Iris Murdoch]

Re: Keep region active after command

[Lennart Borgman]

On Sun, Feb 20, 2011 at 2:16 AM, Miles Bader <miles@gnu.org> wrote:
> Lennart Borgman <lennart.borgman@gmail.com> writes:
>>> No.  Having a function that just sets a variable to nil is silly.
>>
>> ?? Please give an argument!
>
> Because the user may as well just write (setq foo nil)...

Can't that be done instead of using any command ... ;-)

Re: Keep region active after command

[Miles Bader]

Lennart Borgman <lennart.borgman@gmail.com> writes:
>>>> No.  Having a function that just sets a variable to nil is silly.
>>>
>>> ?? Please give an argument!
>>
>> Because the user may as well just write (setq foo nil)...
>
> Can't that be done instead of using any command ... ;-)

Er, by "user" I mean the command.

-miles

-- 
Optimist, n. A proponent of the doctrine that black is white.