* How to report more than 15 small problems with Emacs' documentation?
@ 2016-09-28 11:57 Jorge
2016-09-28 14:51 ` Eli Zaretskii
0 siblings, 1 reply; 3+ messages in thread
From: Jorge @ 2016-09-28 11:57 UTC (permalink / raw)
To: help-gnu-emacs
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?
Regards
--
• 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/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: How to report more than 15 small problems with Emacs' documentation?
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
0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2016-09-28 14:51 UTC (permalink / raw)
To: help-gnu-emacs
> 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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: How to report more than 15 small problems with Emacs' documentation?
2016-09-28 14:51 ` Eli Zaretskii
@ 2016-09-30 17:22 ` Jorge
0 siblings, 0 replies; 3+ messages in thread
From: Jorge @ 2016-09-30 17:22 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: help-gnu-emacs
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/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-09-30 17:22 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).