From: Drew Adams <drew.adams@oracle.com>
To: Marcin Borkowski <mbork@mbork.pl>, Stefan Kangas <stefan@marxist.se>
Cc: "Karl O. Pinc" <kop@meme.com>, 3540@debbugs.gnu.org
Subject: bug#3540: Please reserve a ctrl-key combination for interoperability
Date: Sun, 6 Oct 2019 09:10:59 -0700 (PDT) [thread overview]
Message-ID: <0d884621-5d6e-47c6-8a0e-d70d4c09f15e@default> (raw)
In-Reply-To: <87y2xye4nz.fsf@mbork.pl>
> As a partial solution, the manual *might* suggest to use C-z for that,
> especially that is is bounded to a 99.99% useless command by default
> (and using e.g. screen or tmux makes it 100% useless).
No, please don't do that. IMO:
`C-z' is better used by users and libraries as a
_prefix key_ (by users who are willing to forego
the default binding).
The manual should not suggest that users bind any
particular keys. It's OK for a 3rd-party library
to suggest key bindings. It's not good for Emacs
itself to do that.
3rd-party libraries are opt-in by users. Using
one is like adding its feature/code to your init
file - it's a user choice.
The same isn't true of much of the code distributed
by Emacs. And even when a distributed library (e.g.
`dired-x.el') is opt-in, Emacs should not suggest
bindings for its commands. "Suggestion" by Emacs
is sometimes mistakenly taken by users as a "rule"
or a convention.
There's no good reason for Emacs to suggest that
users use `C-z' for anything particular.
next prev parent reply other threads:[~2019-10-06 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 1:46 bug#3540: Please reserve a ctrl-key combination for interoperability Karl O. Pinc
2010-12-25 11:02 ` bug#3540: reserve a key + inform other gnu package maintainers and mode-authors Arne Babenhauserheide
2019-10-06 4:56 ` bug#3540: Please reserve a ctrl-key combination for interoperability Stefan Kangas
2019-10-06 7:04 ` Marcin Borkowski
2019-10-06 16:10 ` Drew Adams [this message]
2019-10-06 19:39 ` Marcin Borkowski
2019-10-06 21:29 ` Drew Adams
2019-10-09 18:33 ` Marcin Borkowski
2019-10-10 11:04 ` Stefan Kangas
2019-11-17 20:41 ` Stefan Kangas
2019-11-23 23:37 ` Stefan Kangas
2019-10-06 17:38 ` Eli Zaretskii
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=0d884621-5d6e-47c6-8a0e-d70d4c09f15e@default \
--to=drew.adams@oracle.com \
--cc=3540@debbugs.gnu.org \
--cc=kop@meme.com \
--cc=mbork@mbork.pl \
--cc=stefan@marxist.se \
/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).