From: Dani Moncayo <dmoncayo@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 10056@debbugs.gnu.org
Subject: bug#10056: 24.0.91; Mark deactivation
Date: Fri, 25 Jan 2013 20:07:42 +0100 [thread overview]
Message-ID: <CAH8Pv0hc78QPL3XahPNXKZuMskxSj-3jJVmE_PQHm8KLvVntqQ@mail.gmail.com> (raw)
In-Reply-To: <0139B55A9A504DE180FC189491666C53@us.oracle.com>
On Fri, Jan 25, 2013 at 6:41 PM, Drew Adams <drew.adams@oracle.com> wrote:
>> I've just noticed a new case where the mark is not deactivated, when
>> it clearly should (IMO): after `eval-region'.
>
> Why should it?
>
> Even when used interactively (and certainly when not!),
I'm concerned about _interactive_ usability. Sorry if I didn't make
that clear before.
> a user can want to do
> something else with the active region after evaluating it.
>
> Yes, s?he can always hit `C-x C-x C-x C-x' to reactivate it (there is probably a
> shorter way to do it nowadays, but I still have that habit). But the question
> is why? What's the reason to deactivate the region after `eval-region'?
>
> To be clear, I have no particular objection that I can think of offhand. But I
> don't see why the behavior should be changed. "If it ain't broke don't fix it."
> IOW, please argue a bit in favor of the change for this specific command - some
> reasons, please.
Well, the reason is the same for all commands I've mentioned: In my
experience (or my usage pattern), after defining an active region and
invoking a command to operate on it, it's much more likely that the
next commands have nothing to do with that active region. IOW, I
almost always set up an active region to do a single operation on it,
not several ones. So keeping the region active is, at best, counter
intuitive and visually annoying to me.
> Wrt your footnote [2]: Why should we deactivate the region for _any_ command
> when it is called non-interactively? That doesn't make sense to me (yet - but
> I'm willing to learn why).
That footnote is about `narrow-to-region', not about "any command".
But, well, I'm thinking that perhaps the mark deactivation I'm
requesting should be specific to interactive calls. After all, what I
want to avoid is just the annoyance of having to type `C-g' to
deactivate the mark after realizing that Emacs didn't do it for me.
--
Dani Moncayo
next prev parent reply other threads:[~2013-01-25 19:07 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
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 [this message]
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=CAH8Pv0hc78QPL3XahPNXKZuMskxSj-3jJVmE_PQHm8KLvVntqQ@mail.gmail.com \
--to=dmoncayo@gmail.com \
--cc=10056@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).