Subject: bug#10056: 24.0.91; Mark deactivation

From: Dani Moncayo <[email-masked]>
Date: Fri, 25 Jan 2013 13:34:58 +0100

I've just noticed a new case where the mark is not deactivated, when
it clearly should (IMO): after `eval-region'.

So this is the updated list:
  eval-region
  kill-region [1]
  kill-rectangle [1]
  prepend-to-register [4]
  append-to-register [4]
  narrow-to-region [2]
  fill-paragraph [3]
  c-indent-line-or-region [3]
  delete-duplicate-lines [3]
  delete-matching-lines [3]
  delete-non-matching-lines [3]
  delete-blank-lines [3]

--- Footnotes ---

[1] From a read-only buffer, having `kill-read-only-ok' set to nil.
Note that the command does its job in this case, but the mark still
remains active.  Not TRT IMO.

[2] According to Chong, in this case perhaps the mark deactivation
should be made only when the call is interactive.

[3] When the command doesn't alter the buffer text.

[4] When invoked with a prefix argument, from a read-only buffer
(regardless of the value of  `kill-read-only-ok', which doesn't seem
to have any effect on them).

-- 
Dani Moncayo