From: Jorge <jorge13515@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to report more than 15 small problems with Emacs' documentation?
Date: Fri, 30 Sep 2016 14:22:31 -0300 [thread overview]
Message-ID: <CAJR3QneqQDaNhtKY+ma9qZnYEuksLbgf-kvd+Ay8Ux62wOX+uQ@mail.gmail.com> (raw)
In-Reply-To: <838tucoz6q.fsf@gnu.org>
OK. I sent a similar email to the Org Mode mailing list. I had many
Org doc problems to report. Yesterday I reported the first batch,
which took me several hours to prepare. Later I will report the
remaining Org doc problems, and only then I will report the general
Emacs doc problems.
On 28 September 2016 at 11:51, Eli Zaretskii <eliz@gnu.org> wrote:
>> 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.
>
--
• I am Brazilian. I hope my English is correct and I welcome corrections.
• Please adopt free formats like PDF, ODF, Org, LaTeX, Opus, WebM and 7z.
• Free (as in free speech) software for Android: https://f-droid.org/
prev parent reply other threads:[~2016-09-30 17:22 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
2016-09-30 17:22 ` Jorge [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJR3QneqQDaNhtKY+ma9qZnYEuksLbgf-kvd+Ay8Ux62wOX+uQ@mail.gmail.com \
--to=jorge13515@gmail.com \
--cc=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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.