all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Philipp Stephani <p.stephani2@gmail.com>, 22604@debbugs.gnu.org
Subject: bug#22604: 24.5; (elisp) `Key Binding Conventions': what about other `C-c' keys?
Date: Mon, 8 Feb 2016 18:38:47 -0800 (PST)	[thread overview]
Message-ID: <e450220c-35a9-42b8-9f4a-513709dff13a@default> (raw)
In-Reply-To: <CAArVCkT_xoELD9nKV4BOXiDGPHuD1QnbLVNOYR+CfO_A+qh8TA@mail.gmail.com>

> While there, could we also document the conventions for all other
> possible key combinations? What about e.g. keys involving the Meta,
> Super, Hyper, Alt, and Shift modifiers? What about C-F1 etc?

This bug report is about C-c prefixed keys.  We have long had
binding conventions for C-c prefixed keys.

Please file another bug report if you want to suggest conventions
for additional keys.





  reply	other threads:[~2016-02-09  2:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 23:48 bug#22604: 24.5; (elisp) `Key Binding Conventions': what about other `C-c' keys? Drew Adams
2016-02-09  1:13 ` Philipp Stephani
2016-02-09  2:38   ` Drew Adams [this message]
2016-02-09  9:27 ` Andreas Schwab
2016-02-09 15:06   ` Drew Adams
2016-02-09 15:24     ` Andreas Schwab
2016-02-09 15:29       ` Drew Adams
2016-02-09 16:51         ` Andreas Schwab
2016-02-09 17:04         ` Eli Zaretskii
     [not found]         ` <<838u2tddcs.fsf@gnu.org>
2016-02-09 17:24           ` Drew Adams
2016-02-09 18:16             ` Eli Zaretskii
     [not found]         ` << <838u2tddcs.fsf@gnu.org>
     [not found]           ` <<a93a8d1c-5383-4851-a45d-0ccdb7288dab@default>
     [not found]             ` <<83pow5bvgc.fsf@gnu.org>
2016-02-09 18:33               ` Drew Adams
2016-02-09 19:18                 ` Eli Zaretskii
2016-02-09 17:41       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e450220c-35a9-42b8-9f4a-513709dff13a@default \
    --to=drew.adams@oracle.com \
    --cc=22604@debbugs.gnu.org \
    --cc=p.stephani2@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.