unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@suse.de>
Cc: 22604@debbugs.gnu.org
Subject: bug#22604: 24.5; (elisp) `Key Binding Conventions': what about other `C-c' keys?
Date: Tue, 09 Feb 2016 19:41:23 +0200	[thread overview]
Message-ID: <83wpqdbx30.fsf@gnu.org> (raw)
In-Reply-To: <mvma8n9ucsh.fsf@hawking.suse.de> (message from Andreas Schwab on Tue, 09 Feb 2016 16:24:46 +0100)

> From: Andreas Schwab <schwab@suse.de>
> Date: Tue, 09 Feb 2016 16:24:46 +0100
> Cc: 22604@debbugs.gnu.org
> 
> Drew Adams <drew.adams@oracle.com> writes:
> 
> > For example, Lars recently proposed, in bug thread 22172, to bind
> > `C-c +' and `C-c -' by default.  Making the doc clearer about this
> > would preclude such a suggestion, as those keys would fall under
> > the category of "other punctuation", which is reserved for minor modes.
> 
> Then they cannot be used if we follow our conventions.  That looks clear
> enough to me.

Indeed.





      parent reply	other threads:[~2016-02-09 17:41 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
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 [this message]

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=83wpqdbx30.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22604@debbugs.gnu.org \
    --cc=schwab@suse.de \
    /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).