unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: 10056@debbugs.gnu.org
Subject: bug#10056: 24.0.91; Mark deactivation
Date: Sat, 8 Dec 2012 11:09:27 +0100	[thread overview]
Message-ID: <CAH8Pv0hL0kXQ7kGTp3UCOipMoJSwRV4oMnjmW8rFb=D6gRj2PQ@mail.gmail.com> (raw)
In-Reply-To: <CAH8Pv0jBaagJv_3r2hCitMmYpuojGQKEBuyp-UC-Sb=Hb+yTcw@mail.gmail.com>

> As I pointed out previously in this thread, the mark should be
> deactivated (in general - there can be some exceptions) after any
> command that operates on the active region.  Not doing so is annoying,
> because the mark must be deactivated in that cases manually by typing
> `C-g'.
>
> There are still cases where I observe this misbehavior.  Namely:
>
>   kill-region [1]
>   kill-rectangle [1]

>   prepend-to-register
>   append-to-register

I forgot to mention, for the two above commands, that the use case is
"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).

>   narrow-to-region [2]
>   c-indent-line-or-region [3]
>   delete-duplicate-lines [3]
>   delete-matching-lines [3]
>   delete-non-matching-lines [3]
>   delete-blank-lines [3]

Add "fill-paragraph [3]" to the above list.  Important use-case.

> --- 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.


-- 
Dani Moncayo





  reply	other threads:[~2012-12-08 10:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15 20:06 bug#10056: 24.0.91; `copy-to-register' does not deactivate the mark Dani Moncayo
2011-11-15 20:15 ` Dani Moncayo
2011-11-15 20:36   ` Dani Moncayo
2011-11-15 20:18 ` Dani Moncayo
2011-11-21  6:30 ` Chong Yidong
2012-06-05  7:44   ` Dani Moncayo
2012-07-28 19:01   ` Dani Moncayo
2012-07-29  4:45     ` Chong Yidong
2012-07-29  9:46       ` Dani Moncayo
2012-07-29  4:50     ` Chong Yidong
2012-07-29 10:01       ` Dani Moncayo
2012-08-01 21:17         ` Alan Mackenzie
2012-08-01 22:07           ` Dani Moncayo
2012-08-03 21:47             ` Alan Mackenzie
2012-09-08 20:21           ` Stefan Monnier
2012-09-09 20:20             ` Dani Moncayo
2012-09-11 14:42               ` Bastien
2012-12-05  8:04 ` bug#10056: 24.0.91; Mark deactivation Dani Moncayo
2012-12-08 10:09   ` Dani Moncayo [this message]
2012-12-08 23:03     ` Juri Linkov
2012-12-09  0:00       ` Drew Adams
2012-12-09  0:29         ` Juri Linkov
2012-12-09  3:21           ` Drew Adams
2012-12-09  9:07             ` Dani Moncayo
2013-01-25 12:34               ` Dani Moncayo
2013-01-25 17:41                 ` Drew Adams
2013-01-25 19:07                   ` Dani Moncayo
2013-01-25 19:34                     ` Drew Adams
2013-01-25 19:01                 ` Stefan Monnier
2022-04-26 13:50 ` bug#10056: 24.0.91; `copy-to-register' does not deactivate the mark Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH8Pv0hL0kXQ7kGTp3UCOipMoJSwRV4oMnjmW8rFb=D6gRj2PQ@mail.gmail.com' \
    --to=dmoncayo@gmail.com \
    --cc=10056@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).