unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 22604@debbugs.gnu.org
Subject: bug#22604: 24.5; (elisp) `Key Binding Conventions': what about other `C-c' keys?
Date: Mon, 8 Feb 2016 15:48:03 -0800 (PST)	[thread overview]
Message-ID: <38cef267-d54f-40d5-9282-563615551367@default> (raw)

This node mentions about keys following `C-c', but only `{', `}', `<',
`>', `:', `;', control chars, digits, letters, and "other punctuation".

What about keys `-', `+', `@', `#', `%', `^', `&', `*', `=', etc.?  These
are not mentioned.

I think, based on the mention of "other punctuation" coming just after
mention of the explicit list `{', `}', `<', `>', `:', `;',  that all such
chars are intended by "other punctuation".  I guess this because `<' and
`>', at least are not typically punctuation.

Could this doc please corrected to cover the cases of characters not
mentioned that are not really punctuation?  I'd propose that they should
be explicitly covered by what is said for "other punctuation": they
should be reserved for minor modes.

But regardless of what the decision is, even if it is to not put any
restriction on the use of the unmentioned chars, can we please make the
convention explicit in their regard, so there is no question, e.g.,
whether a sequence such as `C-c -' is reserved for minor modes?

Thx.

In GNU Emacs 24.5.1 (i686-pc-mingw32)
 of 2015-04-11 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=3D/c/usr --host=3Di686-pc-mingw32'





             reply	other threads:[~2016-02-08 23:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 23:48 Drew Adams [this message]
2016-02-09  1:13 ` bug#22604: 24.5; (elisp) `Key Binding Conventions': what about other `C-c' keys? 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

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=38cef267-d54f-40d5-9282-563615551367@default \
    --to=drew.adams@oracle.com \
    --cc=22604@debbugs.gnu.org \
    /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).