From: Allen Li <vianchielfaura@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Nicolas Goaziou <mail@nicolasgoaziou.fr>, 28263-done@debbugs.gnu.org
Subject: bug#28263: bug#28263: bug#28263: 24.5; Org: `C-c LETTER' keys
Date: Wed, 6 Dec 2017 12:09:08 -0800 [thread overview]
Message-ID: <CAJr1M6dryTLyXsNt_rXjxsP7Xx=g314T49Oe_n1MDeB95af_2w@mail.gmail.com> (raw)
In-Reply-To: <c6cdf0b9-b15e-407c-a0f6-784757b6719b@default>
On Wed, Dec 6, 2017 at 7:23 AM, Drew Adams <drew.adams@oracle.com> wrote:
> [paraphrased] Org should not suggest user reserved key bindings
I agree with you in general. However, when I first started using
Emacs for Org mode years ago, I found the documentation very helpful.
Furthermore, I did not find the documentation misleading about the
fact that these keys are not standard.
For users that are not accustomed to Emacs, the ability to bind keys
freely is paralyzing. I had no idea what keys would be okay or not
okay to bind.
This could be solved by instead linking to the Emacs key binding
guidelines and pointing out ranges of keys or example keys that would
be safe to bind. I interpret the current documentation as suggesting
such example keys.
For comparison, calendar.el et al do not suggest global key bindings
for their commands. However, Org mode is different because it is one
of Emacs’s "killer apps". It is something that a non-Emacs user would
start using Emacs for. No one is going to switch to Emacs to use
calendar.el, but there are many people that switch to Emacs to use Org
mode. Therefore, there is a benefit in adding some tips for very new
users.
As a matter of practicality, I suspect many users are just blindly
copying Emacs Lisp code from various guides online, so there is no
good way to fight de facto standards from emerging. Projectile is a
particularly blatant offender, a popular package that reserves the C-c
p key for its minor mode.
However, the Emacs documentation is quite clear about key binding
rules. All built in libraries follow it, including Org mode. I do
not interpret the Org documentation as implying otherwise.
next prev parent reply other threads:[~2017-12-06 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <936768a0-1a2e-4a89-8a11-8f1779f8591d@default>
2017-12-04 21:45 ` bug#28263: 24.5; Org: `C-c LETTER' keys Nicolas Goaziou
2017-12-04 22:42 ` Drew Adams
2017-12-05 11:28 ` Nicolas Goaziou
2017-12-05 15:15 ` Drew Adams
2017-12-06 7:58 ` bug#28263: " Allen Li
2017-12-06 7:59 ` Allen Li
2017-12-06 15:23 ` Drew Adams
2017-12-06 20:09 ` Allen Li [this message]
[not found] ` <871shilz7h.fsf@nicolasgoaziou.fr>
2018-02-19 0:26 ` Drew Adams
2018-02-19 9:24 ` Nicolas Goaziou
2018-02-19 16:21 ` Drew Adams
2018-02-20 0:38 ` Nicolas Goaziou
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJr1M6dryTLyXsNt_rXjxsP7Xx=g314T49Oe_n1MDeB95af_2w@mail.gmail.com' \
--to=vianchielfaura@gmail.com \
--cc=28263-done@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=mail@nicolasgoaziou.fr \
/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/org-mode.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).