From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: schwab@suse.de, 22604-done@debbugs.gnu.org
Subject: bug#22604: 24.5; (elisp) `Key Binding Conventions': what about other `C-c' keys?
Date: Tue, 09 Feb 2016 21:18:20 +0200 [thread overview]
Message-ID: <83lh6tbslf.fsf@gnu.org> (raw)
In-Reply-To: <a14d835d-6a57-4af4-9dd8-4d640703d352@default> (message from Drew Adams on Tue, 9 Feb 2016 10:33:28 -0800 (PST))
> Date: Tue, 9 Feb 2016 10:33:28 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: schwab@suse.de, 22604@debbugs.gnu.org
>
> > > 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.
> >
> > Not sure I agree. Usurping too many characters would not be a good
> > idea, IMO.
>
> Usurping? From whom/what?
From users and from other modes.
> It's about reserving this category of keys for minor mode keymaps.
Yes, and I don't think we want or should reserve too many characters.
> > How can such a binding be useful, when Emacs runs on a non-French
> > keyboard? Do we really want to encourage modes that can only be fully
> > functional in some specific locales? I don't think so.
>
> Why treat punctuation and symbols on a US keyboard specially?
> Why should `$' be treated differently from `€'?
Because most keyboards have the former, but not the latter.
> > Any reasons not to close the bug report?
>
> You can close it if you like. I would prefer that we think about
> handling the same category of char-inserting keys (punctuation and
> symbols) for other keyboards the same way we handle those for US
> keyboards. But if that is not to be then it is not to be.
We can think with the bug closed, and we can reopen later (or make a
change without reopening).
next prev parent reply other threads:[~2016-02-09 19:18 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 [this message]
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=83lh6tbslf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22604-done@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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).