From: Drew Adams <drew.adams@oracle.com>
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, 9 Feb 2016 07:06:50 -0800 (PST) [thread overview]
Message-ID: <29ac44ad-3c5d-486e-abd7-a7ef70e906d1@default> (raw)
In-Reply-To: <mvmtwliw7vu.fsf@hawking.suse.de>
> > 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.
>
> Aren't those covered by "other punctuation"? It certainly matches what
> C calls punctuation characters.
As I said, I would like to read it that way also. But there is no
mention of C or punctuation in a programming language, and those
are not usually considered punctuation in English etc., AFAIK.
And then there is the punctuation syntax class - does it mean that
these key conventions change, depending on which chars have
punctuation status in the current syntax table?
I would like the text to be a bit clearer about just what is meant,
including whether the notion of "punctuation" here is meant to
follow syntax class `.' (punctuation).
The bug report asks that we make clear which character keys we mean.
There may be other ones in other languages etc., but at least the
usual such keys on a typical US keyboard should be considered (and
so mentioned) as falling under what is said for "other punctuation".
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.
next prev parent reply other threads:[~2016-02-09 15:06 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 [this message]
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=29ac44ad-3c5d-486e-abd7-a7ef70e906d1@default \
--to=drew.adams@oracle.com \
--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 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.