From: Dani Moncayo <dmoncayo@gmail.com>
To: Chong Yidong <cyd@gnu.org>
Cc: 10056@debbugs.gnu.org
Subject: bug#10056: 24.0.91; `copy-to-register' does not deactivate the mark
Date: Sun, 29 Jul 2012 11:46:41 +0200 [thread overview]
Message-ID: <CAH8Pv0g97Nj8yvgKX65qOmBgeK8TUH-3k3LFp+5XKhjueAP2fQ@mail.gmail.com> (raw)
In-Reply-To: <87fw8buqdc.fsf@gnu.org>
> I left prepend-to-register and append-to-register alone for now; there
> may be cases where users want to keep the mark active for those
> commands, but I'm not certain.
I can't imagine such cases right now, but my imagination is limited :)
> As for C-x r k on read-only buffers, the mark is now deactivated, but
> only if kill-read-only-ok is non-nil (similar to C-w).
?? I don't see such behavior in a recent build of the trunk. I've
just tested C-x r k (from Emacs -Q, in an Info buffer), and the mark
is not deactivated, even if kill-read-only-ok is non-nil. IMO, the
mark should definitely be deactivated in this case.
And what is more, when kill-read-only-ok is nil, "C-x r k" still does
its job (despite the error message shown in the echo area), i.e., it
saves the rectangle contents. Therefore, this is confusing from my
POV. IMO, either the command should do nothing in this case (no
rectangle text gets saved), or, if the intention is to save the
rectangle also in this case, the mark should be deactivated, because
not doing so gives (me) the wrong impression, i.e, that the command
has been cancelled and nothing more happened.
--
Dani Moncayo
next prev parent reply other threads:[~2012-07-29 9:46 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 [this message]
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
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=CAH8Pv0g97Nj8yvgKX65qOmBgeK8TUH-3k3LFp+5XKhjueAP2fQ@mail.gmail.com \
--to=dmoncayo@gmail.com \
--cc=10056@debbugs.gnu.org \
--cc=cyd@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).