From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: schwab@suse.de, 22604@debbugs.gnu.org
Subject: bug#22604: 24.5; (elisp) `Key Binding Conventions': what about other `C-c' keys?
Date: Tue, 9 Feb 2016 09:24:03 -0800 (PST) [thread overview]
Message-ID: <a93a8d1c-5383-4851-a45d-0ccdb7288dab@default> (raw)
In-Reply-To: <<838u2tddcs.fsf@gnu.org>>
> > > > 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.
> >
> > You feel that the convention is clear enough for you.
> >
> > Although I might agree with your interpretation of the convention
> > as currently stated, I would like it to be stated more clearly,
> > explicitly saying what it means by "punctuation", for example.
>
> It's not really easy to define "punctuation" here. More importantly,
> some of the characters that _are_ reserved aren't punctuation by
> Unicode categorization (they are symbols).
>
> Would it help if we said "ASCII punctuation and symbol characters"?
> That's the official name of those characters, AFAICT, and the "ASCII"
> part makes sure no one will think about non-ASCII punctuation
> characters, which I think we don't want to reserve.
>
> Enumerating the characters can be tedious, so I think we'd like to
> avoid that.
Yes, "punctuation and symbol characters" helps, IMO. That was
one of my points: the chars are not necessarily punctuation, in
the usual sense of the word.
Dunno whether it's good to limit it to ASCII. At a minimum it
should cover the "punctuation and symbol character" keys on a
typical US keyboard, of course. Whether it should also cover
other punctuation or other symbol chars is maybe an open question.
It's really about character-inserting keys on a keyboard, not
punctuation and symbol chars that are not on keys.
But a key on a French keyboard that inserts a left guillemet
char should, I think, be handled the same by the convention as
is a key on a US keyboard that inserts a double-quote char or
a left angle-bracket char.
IOW, can/should we not apply the idea of such keys to keyboards
that insert other than ASCII chars?
I do agree that exhaustive enumeration would not be helpful.
next prev parent reply other threads:[~2016-02-09 17:24 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 [this message]
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=a93a8d1c-5383-4851-a45d-0ccdb7288dab@default \
--to=drew.adams@oracle.com \
--cc=22604@debbugs.gnu.org \
--cc=eliz@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.