From: Drew Adams <drew.adams@oracle.com>
To: Tatsu Takamaro <tatsu.takamaro@gmail.com>,
Yuri Khan <yuri.v.khan@gmail.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Q1 - the keys' bindings to work more widely
Date: Thu, 19 Dec 2024 02:13:37 +0000 [thread overview]
Message-ID: <DS7PR10MB5232BD49526F42B823FF842CF3062@DS7PR10MB5232.namprd10.prod.outlook.com> (raw)
In-Reply-To: <5b491f22-03e0-4fde-0a81-0c9d1e50a3b0@gmail.com>
>> I must note that you’re in for a lot of swimming against the current
>> if you want to reclaim C-c from its established Emacs role as a prefix.
>> A lot of modes bind some of their functionality to sequences
>> starting with C-c, and you will either have to rebind them in order to
>> start using them, or they will wrest C-c back from you.
>
> As far as I read in the Emacs conventions, the C-c is reserved for users,
> so other modes should not use it.
No, read the doc again. This is what it tells Elisp coders:
Don’t define ‘C-c LETTER’ as a key in Lisp programs. Sequences
consisting of ‘C-c’ and a letter (either upper or lower case) are
reserved for users; they are the *only* sequences reserved for
users, so do not block them.
Only C-c followed by a _letter_ is reserved for users.
It then goes on to speak about conventions for other bindings
with prefix key `C-c', i.e., those with only letters after the
prefix.
next prev parent reply other threads:[~2024-12-19 2:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 23:46 Q1 - the keys' bindings to work more widely Tatsu Takamaro
2024-12-15 2:15 ` [External] : " Drew Adams
2024-12-16 23:11 ` Tatsu Takamaro
2024-12-16 23:55 ` Drew Adams via Users list for the GNU Emacs text editor
2024-12-17 0:05 ` Drew Adams
2024-12-17 0:16 ` Tatsu Takamaro
2024-12-17 2:17 ` Drew Adams
2024-12-17 5:41 ` Tatsu Takamaro
2024-12-17 6:28 ` Yuri Khan
2024-12-18 22:14 ` Tatsu Takamaro
2024-12-19 2:13 ` Drew Adams [this message]
2024-12-17 5:42 ` Tatsu Takamaro
2024-12-15 10:05 ` Alain.Cochard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DS7PR10MB5232BD49526F42B823FF842CF3062@DS7PR10MB5232.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tatsu.takamaro@gmail.com \
--cc=yuri.v.khan@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.