From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30530-done@debbugs.gnu.org
Subject: bug#30530: 26.0; Emacs manual: mention (1) user-reserved keys, (2) users can bind any keys
Date: Sat, 24 Feb 2018 22:27:48 +0100 [thread overview]
Message-ID: <87zi3y13jf.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <83h8q62sgd.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 24 Feb 2018 19:44:18 +0200")
Hello,
Eli Zaretskii <eliz@gnu.org> writes:
> I added some text about the latter, although I seriously doubt that it
> will be discoverable enough to make any difference.
Thank you.
For good measure, could you also add a @cindex about it? E.g,
@cindex user reserved key bindings
For reference, this bug report stems from the following part of the Org
manual:
For a better experience, the three Org commands ~org-store-link~,
~org-capture~ and ~org-agenda~ ought to be accessible anywhere in
Emacs, not just in Org buffers. To that effect, you need to bind them
to globally available keys, like the ones reserved for users (see
[[info:elisp::Key%20Binding%20Conventions]]). Here are suggested
bindings, please modify the keys to your own liking.
#+begin_src emacs-lisp
(global-set-key "\C-cl" 'org-store-link)
(global-set-key "\C-ca" 'org-agenda)
(global-set-key "\C-cc" 'org-capture)
#+end_src
Drew pointed out that suggesting to bind user reserved keys was almost
as if we were binding them.
I can hear that argument, and would happily stop the paragraph at
"globally available keys". However, I have the feeling this deserves
a cross-reference, and an appendix in the Elisp manual doesn't sound
like an appropriate location.
Regards,
--
Nicolas Goaziou 0x80A93738
next prev parent reply other threads:[~2018-02-24 21:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<f630bd00-a129-48ec-8788-2ed09964b598@default>
[not found] ` <<83lgfi4qw2.fsf@gnu.org>
2018-02-24 17:00 ` bug#30530: 26.0; Emacs manual: mention (1) user-reserved keys, (2) users can bind any keys Drew Adams
2018-02-24 17:44 ` Eli Zaretskii
2018-02-24 21:27 ` Nicolas Goaziou [this message]
2018-03-01 15:44 ` Eli Zaretskii
[not found] ` <<87zi3y13jf.fsf@nicolasgoaziou.fr>
[not found] ` <<83d10nyf4y.fsf@gnu.org>
2018-03-01 17:31 ` Drew Adams
2018-03-01 19:22 ` Eli Zaretskii
2018-03-01 19:30 ` Noam Postavsky
[not found] ` <<<87zi3y13jf.fsf@nicolasgoaziou.fr>
[not found] ` <<<83d10nyf4y.fsf@gnu.org>
[not found] ` <<92c8fd97-8e96-4e2b-8706-f5ca97869912@default>
[not found] ` <<831sh3y51x.fsf@gnu.org>
2018-03-01 21:00 ` Drew Adams
2018-03-01 21:33 ` Noam Postavsky
2018-03-02 5:32 ` Eli Zaretskii
[not found] ` <<<<87zi3y13jf.fsf@nicolasgoaziou.fr>
[not found] ` <<<<83d10nyf4y.fsf@gnu.org>
[not found] ` <<<92c8fd97-8e96-4e2b-8706-f5ca97869912@default>
[not found] ` <<<831sh3y51x.fsf@gnu.org>
[not found] ` <<eea83f2b-2dea-49c6-941d-5db34a741a5d@default>
[not found] ` <<83woyvvy8g.fsf@gnu.org>
2018-03-02 15:17 ` Drew Adams
2018-03-02 15:49 ` Eli Zaretskii
2018-02-19 16:16 Drew Adams
2018-02-24 10:35 ` 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=87zi3y13jf.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=30530-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).