From: "Drew Adams" <drew.adams@oracle.com>
To: "'chad'" <yandros@mit.edu>
Cc: 'Emacs-Devel devel' <emacs-devel@gnu.org>
Subject: RE: Binding M-n and M-p to forward-paragraph and backward-paragraphrespectively
Date: Sat, 9 Apr 2011 12:26:45 -0700 [thread overview]
Message-ID: <3F8DEC90BBA94708866F7CC70C4D5067@us.oracle.com> (raw)
In-Reply-To: <7C30351A-8431-44CA-BBEF-06AC0E509EBC@mit.edu>
> >> the idea that we shouldn't add new bindings because then
> >> someone in the future might think that those bindings are
> >> somehow `special' - and that we might want them to think
> >> otherwise - is a rather extreme combination of straw-man and
> >> absurdity.
> >
> > It is neither straw man nor absurdity. And it is not just
> > an idea. The last go-round about binding some (function)
> > key by default clearly demonstrated this: The discussion
> > had not even finished, and no decision had yet been reached,
> > before some were sending in posts that indicated that they
> > understood that the key was _reserved_ and should not be
> > changed by users or 3rd-party libraries.
>
> Yes, where as this is a binding that is clearly intended to
> be changed by users and 3rd-party libraries.
No, that was true also in the other case, as it is in most cases where a binding
is explicitly only for _default_ behavior.
That's the point: Some people _mis_understand, thinking that the existence of a
default binding means that the binding is in some way reserved. And as I
mentioned, the more a default key gets used commonly, the more people shy away
from rebinding it. Creating a default binding is not without behavioral
consequences.
next prev parent reply other threads:[~2011-04-09 19:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 13:57 Binding M-n and M-p to forward-paragraph and backward-paragraph respectively Deniz Dogan
2011-04-07 16:33 ` Binding M-n and M-p to forward-paragraph and backward-paragraphrespectively Drew Adams
2011-04-07 17:57 ` Sean Sieger
2011-04-07 18:15 ` Binding M-n and M-p to forward-paragraph andbackward-paragraphrespectively Drew Adams
2011-04-07 18:24 ` Sean Sieger
2011-04-07 18:28 ` Binding M-n and M-p to forward-paragraphandbackward-paragraphrespectively Drew Adams
2011-04-07 18:29 ` Sean Sieger
2011-04-07 20:31 ` Antoine Levitt
2011-04-07 20:53 ` Binding M-n and M-p toforward-paragraphandbackward-paragraphrespectively Drew Adams
2011-04-08 3:13 ` Davis Herring
2011-04-08 8:09 ` Andreas Röhler
2011-04-07 22:30 ` Binding M-n and M-p to forward-paragraphandbackward-paragraphrespectively David De La Harpe Golden
2011-04-08 10:19 ` Antoine Levitt
2011-04-08 21:48 ` Lennart Borgman
2011-04-09 1:40 ` Binding M-n and M-p to forward-paragraph and backward-paragraph respectively Stefan Monnier
2011-04-09 4:10 ` chad
2011-04-09 15:24 ` Binding M-n and M-p to forward-paragraph and backward-paragraphrespectively Drew Adams
2011-04-09 19:09 ` chad
2011-04-09 19:26 ` Drew Adams [this message]
2011-04-10 2:49 ` Leo
2011-04-10 3:10 ` chad
2011-04-10 5:37 ` Leo
2011-04-10 9:15 ` Stephen J. Turnbull
2011-04-10 13:17 ` Lennart Borgman
2011-04-09 21:29 ` Davis Herring
2011-04-09 22:50 ` PJ Weisberg
2011-04-09 19:30 ` Binding M-n and M-p to forward-paragraph and backward-paragraph respectively Chong Yidong
2011-04-10 3:33 ` Stefan Monnier
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=3F8DEC90BBA94708866F7CC70C4D5067@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=yandros@mit.edu \
/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).