unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: "gregory@heytings.org" <gregory@heytings.org>,
	"stefan@marxist.se" <stefan@marxist.se>,
	"50880@debbugs.gnu.org" <50880@debbugs.gnu.org>
Subject: bug#50880: [External] : bug#50880: Add "Contributing to Emacs" help command (see C-h C-h)
Date: Fri, 1 Oct 2021 17:08:04 +0000	[thread overview]
Message-ID: <CO6PR10MB54732608F9C4DB63FD33906BF3AB9@CO6PR10MB5473.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83r1d5dn7o.fsf@gnu.org>

> And I already said what I think about it: to me it sounds like a waste
> to reserve a C-h key for that.  It doesn't even belong to "help" per
> se, IMO.

+1.

Just because some key is not yet taken, that's not a
good reason to assign it eagerly or willy nilly.

And to me this sounds like such an assignment - this
doesn't need a key sequence.  The need identified
was just to call more attention to it.





  reply	other threads:[~2021-10-01 17:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 22:55 bug#50880: Add "Contributing to Emacs" help command (see C-h C-h) Stefan Kangas
2021-09-29  7:06 ` Lars Ingebrigtsen
2021-09-29  9:11   ` Stefan Kangas
2021-09-29  9:18     ` Gregory Heytings
2021-09-29  9:41       ` Stefan Kangas
2021-09-29 16:55         ` Juri Linkov
2021-09-29 17:41           ` Stefan Kangas
2021-09-29 17:45             ` Lars Ingebrigtsen
2021-09-29 17:55           ` Eli Zaretskii
2021-09-29 18:36           ` Gregory Heytings
2021-09-29 16:00     ` Lars Ingebrigtsen
2021-09-29 16:52       ` Stefan Kangas
2021-09-30  1:10         ` Stefan Kangas
2021-09-30  6:10           ` Lars Ingebrigtsen
2021-09-30  7:49           ` Gregory Heytings
2021-09-30 11:51             ` Gregory Heytings
2021-09-30 20:01             ` Stefan Kangas
2021-10-01  7:24               ` Lars Ingebrigtsen
2021-10-01 10:17                 ` Eli Zaretskii
2021-10-01 10:20                   ` Lars Ingebrigtsen
2021-10-01 10:28                     ` Eli Zaretskii
2021-10-01 10:32                       ` Lars Ingebrigtsen
2021-10-01 11:00                         ` Eli Zaretskii
2021-10-01 17:08                           ` Drew Adams [this message]
2021-10-01 18:45                           ` Stefan Kangas
2021-10-01 18:58                             ` Eli Zaretskii
2021-10-02 23:17                   ` Richard Stallman
2021-10-02 23:51                     ` Stefan Kangas
2021-10-03  5:57                     ` Eli Zaretskii
2021-10-03 11:55                       ` Stefan Kangas
2021-10-03 19:10                         ` Gregory Heytings

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=CO6PR10MB54732608F9C4DB63FD33906BF3AB9@CO6PR10MB5473.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=50880@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gregory@heytings.org \
    --cc=larsi@gnus.org \
    --cc=stefan@marxist.se \
    /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).