From: "Philip K." <philipk@posteo.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel <emacs-devel@gnu.org>,
Thibaut Verron <thibaut.verron@gmail.com>,
"T.V Raman" <raman@google.com>
Subject: Re: Emacs default key bindings [was: Opening Up More Keymaps Re: Standardizing more key bindings?]
Date: Fri, 02 Oct 2020 21:21:27 +0200 [thread overview]
Message-ID: <87wo08ph6w.fsf@posteo.net> (raw)
In-Reply-To: <364afb35-1cf9-4bd8-a34d-370dc428f950@default> (Drew Adams's message of "Fri, 2 Oct 2020 11:14:48 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> 3. There's been a tendency recently to give Emacs
> even more default key bindings. Two cases come
> to mind, both in 2020:
>
> a. `C-x p' was taken by Emacs as a prefix key for
> `project.el' commands.
> b. `C-x t' was taken by Emacs as a prefix key for
> `tabbar.el' commands.
>
> Maybe those deserve prefix keys (?). But you see
> the tendency - less and less for users; more taken
> by default bindings.
>
> That's 2 excellent prefix keys just removed, in
> effect, from the user/3rd-party space. Poof!
I get that they were in effect removed from the 3rd-party space, but the
user is still the final arbiter in what is bound or not. Do you really
loose anything, if you rebind C-x p, if you don't use project.el? Same
goes for C-x t if you don't use tabs.
My point is that there seem to be varying degrees of importance to
key-bindings: Rebinding C-c, let alone a self-insert key is far more
disruptive than M-/, C-o, C-x, C-x a, etc. -- it's just difficult to
draw the line.
--
Philip K.
next prev parent reply other threads:[~2020-10-02 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 18:14 Emacs default key bindings [was: Opening Up More Keymaps Re: Standardizing more key bindings?] Drew Adams
2020-10-02 19:21 ` Philip K. [this message]
2020-10-02 20:41 ` Drew Adams
2020-10-02 19:24 ` Ergus
2020-10-02 20:45 ` Drew Adams
2020-10-02 22:31 ` Philip K.
2020-10-02 22:50 ` Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2020-10-02 18:46 arthur miller
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=87wo08ph6w.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=raman@google.com \
--cc=thibaut.verron@gmail.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).