From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 30530@debbugs.gnu.org, mail@nicolasgoaziou.fr
Subject: bug#30530: 26.0; Emacs manual: mention (1) user-reserved keys, (2) users can bind any keys
Date: Thu, 1 Mar 2018 13:00:37 -0800 (PST) [thread overview]
Message-ID: <eea83f2b-2dea-49c6-941d-5db34a741a5d@default> (raw)
In-Reply-To: <<831sh3y51x.fsf@gnu.org>>
> > The Emacs doc makes clear that these keys are reserved for users.
>
> Being reserved means that users can bind them.
You keep repeating that, but it has never been in question.
> > Users do not need a library to instruct them to co-opt
> > the keys for its use.
>
> No, it's not a library that "instructs" them, it's a document that
> tells them they could bind these keys for their own convenience.
We can perhaps agree to disagree about that, as well as
perhaps about the likely result of users, particularly
newbies, following that Org-doc recommendation.
> > I'm surprised that you would endorse this.
> > There is no need for it, and it is not helpful.
>
> I think I'm entitled to my opinions
Of course you are. No one said anything to the contrary.
> even if you consider them unhelpful (unhelpful to what,
> may I wonder?).
Please read what I wrote. I did not say that your opinions
are unhelpful.
It is the practice that was the subject of bug #28263, and
that you seem to endorse, that I said users do not need and
is not helpful (for users, obviously).
The Org doc does not need to recommend that users bind
reserved user keys to Org commands, and doing so is (IMHO)
unhelpful to users.
Just one opinion, of course.
next prev parent reply other threads:[~2018-03-01 21:00 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
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 [this message]
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=eea83f2b-2dea-49c6-941d-5db34a741a5d@default \
--to=drew.adams@oracle.com \
--cc=30530@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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.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).