From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: How to report more than 15 small problems with Emacs' documentation?
Date: Wed, 28 Sep 2016 17:51:09 +0300 [thread overview]
Message-ID: <838tucoz6q.fsf@gnu.org> (raw)
In-Reply-To: <CAJR3QncazGuJ8PHC1qsfQav5zky06W4i+ExikPY6PTqDmUBnuw@mail.gmail.com> (message from Jorge on Wed, 28 Sep 2016 08:57:24 -0300)
> From: Jorge <jorge13515@gmail.com>
> Date: Wed, 28 Sep 2016 08:57:24 -0300
>
> Hello. I have noted a number (more than 15) of small problems with Emacs'
> documentation. For example, [[info:emacs#Yes or No Prompts]] has these two
> problems:
> 1. It swaps M-v with C-v.
> 2. In the last paragraph it says:
> #+BEGIN_QUOTE
> use the history commands ‘M-p’ and ‘M-f’, etc.
> #+END_QUOTE
> It probably meant M-n instead of M-f.
>
> Should I report one bug for all the problems? Or should I report one bug for
> each affected manual section or docstring?
For such minor problems, I think even a single report with all of them
would be OK.
Thanks.
next prev parent reply other threads:[~2016-09-28 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 11:57 How to report more than 15 small problems with Emacs' documentation? Jorge
2016-09-28 14:51 ` Eli Zaretskii [this message]
2016-09-30 17:22 ` Jorge
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=838tucoz6q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).