unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: 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, 01 Mar 2018 21:22:18 +0200	[thread overview]
Message-ID: <831sh3y51x.fsf@gnu.org> (raw)
In-Reply-To: <92c8fd97-8e96-4e2b-8706-f5ca97869912@default> (message from Drew Adams on Thu, 1 Mar 2018 09:31:13 -0800 (PST))

> Date: Thu, 1 Mar 2018 09:31:13 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: drew.adams@oracle.com, 30530@debbugs.gnu.org
> 
> The Emacs doc makes clear that these keys are reserved for users.

Being reserved means that users can bind them.

> 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.

> 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 even if you consider them
unhelpful (unhelpful to what, may I wonder?).





  reply	other threads:[~2018-03-01 19:22 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 [this message]
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=831sh3y51x.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=30530@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.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).