From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: gregory@heytings.org, stefan@marxist.se, 50880@debbugs.gnu.org
Subject: bug#50880: Add "Contributing to Emacs" help command (see C-h C-h)
Date: Fri, 01 Oct 2021 13:17:45 +0300 [thread overview]
Message-ID: <83zgrtdp6e.fsf@gnu.org> (raw)
In-Reply-To: <87a6jtw6ki.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 01 Oct 2021 09:24:45 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Fri, 01 Oct 2021 09:24:45 +0200
> Cc: Gregory Heytings <gregory@heytings.org>, 50880@debbugs.gnu.org
>
> Stefan Kangas <stefan@marxist.se> writes:
>
> >> What was wrong with
> >>
> >> C-h g -> About the GNU project
> >> C-h G -> Emacs copying permission (GNU General Public License)
> >> C-h C-c -> Contributing
> >
> > IMO the best proposal so far, but Lars didn't want to move the GPL
> > from 'C-h C-c' so that part unfortunately makes it a non-starter.
>
> I'm not dead set against it -- it's not like these are commands that
> people use heavily. But that cuts the other way, too -- making this new
> command mnemonic isn't really that important, either, since I'd assume
> that people would be accessing them via `C-h C-h' and then paging down,
> entering whatever key it says they should use. I.e., nobody's
> remembering these keystrokes anyway.
>
> Perhaps Eli has an opinion here?
How about not giving it a key binding at all? Why is a key binding
important in this case? It's not like people will want to read that
section twice a day.
> >> Also, I would put "Contributing to Emacs" in the first subsection of
> >> "Miscellaneous", after "Debugging Emacs", where it belongs. Which by the
> >> way makes me wonder why Emacs TODO is not there, too. It would perhaps be
> >> even better to create a third subsection with
> >>
> >> C-p Known problems
> >> C-d Debugging Emacs
> >> ? Contributing to Emacs
> >> C-t Emacs TODO
> >
> > Good idea, I like it.
>
> Me too.
Which part? If this is about the manual organization, I fail to see
what's wrong with the current one, where Contributing is a chapter --
you don't get any more prominent than that.
next prev parent reply other threads:[~2021-10-01 10:17 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 [this message]
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 ` bug#50880: [External] : " Drew Adams
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=83zgrtdp6e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50880@debbugs.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).