From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 10899@debbugs.gnu.org
Subject: bug#10899: 24.0.93; c-forward-conditional should not move the mark
Date: Tue, 28 Feb 2012 08:42:43 +0100 [thread overview]
Message-ID: <CAH8Pv0hF+yd5ui3gmFfBAtyT3i0kB=q3Vz=59-fdtder_jZN1A@mail.gmail.com> (raw)
In-Reply-To: <CAH8Pv0jA22K9TmKBiFEc+BguFmpOXqbkUf+QcQKp7dwhB+DUmg@mail.gmail.com>
> Consistency is a good design principle to follow, unless there is good
> reason not to. And frankly, I don't see a good reason here.
...and I'll explain why:
Well-known movement commands like `M-<', `M->' or the search commands
set the mark (IMO) because they meet two criteria:
1. They may move point to a distant location.
2. There is not an "inverse" command to move point back to the
original position (or near it): commands like `forward-list' or
`forward-page' meet criterion #1, but they don't set the mark because
you have `backward-list' and `backward-page' to move to the original
position.
And when command meet these two criteria, it should set the mark, but
only if it is inactive, because when the mark is active, the user
surely wants to extend the _current_ region, i.e., "leave the mark
alone where I've set it, and just move the point".
IMO, this is the behavior users expect, and are used to.
Summarizing:
a. `c-forward-conditional' and `c-backward-conditional' should not set
the mark, because each one has an inverse movement command.
b. Even if you disagree, those commands should not set the mark when
it is active.
--
Dani Moncayo
next prev parent reply other threads:[~2012-02-28 7:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 19:06 bug#10899: 24.0.93; c-forward-conditional should not move the mark Dani Moncayo
2012-02-27 19:29 ` Dani Moncayo
2012-02-27 20:28 ` Eli Zaretskii
2012-02-27 20:59 ` Dani Moncayo
2012-02-28 7:42 ` Dani Moncayo [this message]
2012-02-28 10:30 ` Juri Linkov
2012-02-28 11:12 ` Dani Moncayo
2012-02-29 0:14 ` Juri Linkov
2012-02-28 21:59 ` Stefan Monnier
2020-08-25 12:34 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH8Pv0hF+yd5ui3gmFfBAtyT3i0kB=q3Vz=59-fdtder_jZN1A@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=10899@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.