From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, pogonyshev@gmx.net
Subject: Re: `inhibit-mark-movement'
Date: Mon, 13 Dec 2004 14:51:47 -0500 [thread overview]
Message-ID: <E1CdwEV-0005UG-6b@fencepost.gnu.org> (raw)
In-Reply-To: <874qiwm8sq.fsf@jurta.org> (message from Juri Linkov on Thu, 09 Dec 2004 03:48:05 +0200)
Currently M-C-SPC starts marking a new region even in the region is
active. But to start a new region it is possible to deactivate the
current region with C-g, and start a new marking. So it's not
a problem. There was no release where consequent marking commands
extend the region. So it's not too late to change this behavior.
This change also allows to do such useful things as switching the
direction of the region marking, i.e. M-C-SPC C-x C-x M-C-SPC M-C-SPC
and it continues extending the region in the reverse direction towards
the beginning of the buffer. Another C-x C-x M-C-SPC and it continues
extending the marked region forwards again.
It sounds like a good change. Stefan, are you convinced?
next prev parent reply other threads:[~2004-12-13 19:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 0:56 `inhibit-mark-movement' Paul Pogonyshev
2004-12-08 3:08 ` `inhibit-mark-movement' Stefan Monnier
2004-12-08 15:40 ` `inhibit-mark-movement' Paul Pogonyshev
2004-12-08 16:59 ` `inhibit-mark-movement' Stefan Monnier
2004-12-08 17:59 ` `inhibit-mark-movement' Juri Linkov
2004-12-08 19:22 ` `inhibit-mark-movement' Stefan Monnier
2004-12-09 1:48 ` `inhibit-mark-movement' Juri Linkov
2004-12-13 19:51 ` Richard Stallman [this message]
2004-12-13 23:17 ` `inhibit-mark-movement' Stefan Monnier
2004-12-14 10:55 ` `inhibit-mark-movement' Juri Linkov
2004-12-14 11:24 ` `inhibit-mark-movement' Stefan Monnier
2004-12-17 16:11 ` `inhibit-mark-movement' Juri Linkov
2004-12-20 10:56 ` `inhibit-mark-movement' Richard Stallman
2004-12-08 3:29 ` `inhibit-mark-movement' Juri Linkov
2004-12-08 3:46 ` `inhibit-mark-movement' Juri Linkov
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=E1CdwEV-0005UG-6b@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=pogonyshev@gmx.net \
/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).