From: Drew Adams <drew.adams@oracle.com>
To: Michael Welsh Duggan <mwd@md5i.com>, emacs-devel@gnu.org
Subject: RE: C-x SPC : rectangle-mark-mode or gud-break?
Date: Thu, 19 Dec 2013 13:41:45 -0800 (PST) [thread overview]
Message-ID: <fbec30c5-7ccf-4523-bd74-9e49af1d49f9@default> (raw)
In-Reply-To: <8738lo7hbz.fsf@maru2.md5i.com>
> I know I am opening up a can of worms here, but I am going to argue that
> `C-x SPC' be changed back to `gud-break'.
1. `gud-break' should never have been given a global binding on prefix
`C-x'. It is fine for it to have a binding on `gud-key-prefix', i.e.,
`C-x C-a'. Why does it need a global binding? And if it really does,
for some reason, why sacrifice such an important global prefix key as
`C-x' for it?
2. `C-x SPC' should never have been given as a global key binding to
`rectangle-mark-mode'.
`C-x SPC' should be left UNbound. If and when a library or Emacs itself
binds `C-x SPC', there should be good reasons for that. Other things
being equal, if bound, `C-x SPC' should be used as a prefix key, letting
users take advantage of `C-x SPC SPC SPC...' for a repeatable command.
There is no good reason (none) to bind `C-x SPC' to `rectangle-mark-mode'
in the global map. That command should have been put on prefix key
`C-x r', like the other rectangle commands. `C-x' is far too precious
to waste on this.
AFAICT, not one argument was ever given in favor of binding `C-x SPC'
to `rectangle-mark-mode'. The only real support for it was this
non-argument from Eli: "`C-x SPC' is available", followed by "Why is
everybody ignoring the `C-x SPC' suggestion?"
And all objections to this binding, including the reasons given
against, were simply ignored. The only replies to the objections were
messages in support of the objections - also ignored.
http://lists.gnu.org/archive/html/emacs-devel/2013-11/msg00046.html
next prev parent reply other threads:[~2013-12-19 21:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 19:48 C-x SPC : rectangle-mark-mode or gud-break? Michael Welsh Duggan
2013-12-19 21:41 ` Drew Adams [this message]
2013-12-20 0:12 ` Michael Welsh Duggan
2013-12-20 1:56 ` Drew Adams
2013-12-20 2:34 ` Stephen J. Turnbull
2013-12-20 3:35 ` Drew Adams
2013-12-20 5:07 ` Stephen J. Turnbull
2014-01-15 18:33 ` Stefan Monnier
2014-01-15 18:46 ` Michael Welsh Duggan
2014-01-15 23:45 ` Stefan Monnier
2014-01-16 0:39 ` Michael Welsh Duggan
2014-01-16 4:14 ` Stefan Monnier
[not found] ` <CAM9Zgm0X=3PQYQvc6Pg6iDgRRKRs1bQ9wPU=gOP7xF9KdX40-w@mail.gmail.com>
[not found] ` <jwv61pkrri0.fsf-monnier+emacs@gnu.org>
2014-01-16 13:47 ` Bozhidar Batsov
2014-01-17 12:45 ` Bastien
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=fbec30c5-7ccf-4523-bd74-9e49af1d49f9@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=mwd@md5i.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).