From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Drew Adams <drew.adams@oracle.com>
Cc: 28263-done@debbugs.gnu.org
Subject: bug#28263: 24.5; Org: `C-c LETTER' keys
Date: Tue, 05 Dec 2017 12:28:27 +0100 [thread overview]
Message-ID: <87h8t59zxg.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <0f47b7da-82d7-4521-aaf6-f2430876ccc2@default> (Drew Adams's message of "Mon, 4 Dec 2017 14:42:54 -0800 (PST)")
Hello,
Drew Adams <drew.adams@oracle.com> writes:
>> > Dunno whether there are actual bindings in Org that correspond to these
>> > occurrences in the source code of `C-c' followed by a letter. Might be
>> > worth checking. (Bindings of `C-c' followed by a letter are reserved
>> > for users.) Possibly these are just vestigial doc indications, which
>> > could be corrected/updated.
>>
>> Org's manual suggests to bind `org-agenda' to `C-c a', but doesn't bind
>> it by default.
>
> I'm not even sure that's a great idea. I think not.
>
> I suppose it's "legit", as the user, not the Org code, would be
> making the binding. But in my libraries I provide binding
> suggestions only for keys that are not reserved for use by users.
>
> If a commonly used Emacs library (Org is the best example of that)
> suggests to users that they bind `C-c a' to something then that
> key becomes pretty much, in effect, lost as a key reserved for
> user customization.
>
> IOW, if 90% of Emacs users follow that suggestion then there is
> little difference between that situation and the situation of
> Org binding `C-c a' by default.
>
> My vote would be that Org should not do this. Just one opinion.
I understand your concern. However, Org tries to be as neutral as
possible with this. Quoting the manual:
The manual suggests a few global key bindings, in particular @kbd{C-c a} for
@code{org-agenda} and @kbd{C-c c} for @code{org-capture}. These are only
suggestions, but the rest of the manual assumes that these key bindings are in
place in order to list commands by key access.
As explained here, this "suggestion" is only necessary to clarify key
bindings in the manual. `org-agenda' and `org-capture' bindings are
really prefixes for many other commands. Having to write, e.g., "the
prefix you chose for `org-agenda' then #" instead of "C-c a #" would be
a lot more verbose, and ultimately, cripple documentation.
I think the current state is quite fair.
Regards,
--
Nicolas Goaziou 0x80A93738
next prev parent reply other threads:[~2017-12-05 11:29 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 [this message]
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 ` bug#28263: " Allen Li
[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=87h8t59zxg.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=28263-done@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).