Hi, Lele

Thank you very much for proof-reading the doc. I make a lot of silly
mistakes.

I wonder if you've read the docstrings in the .el files, too, since that's
where most of the new documentation is right now.

> Will make a proper bug report with a patch, if you prefer:

Neither of those is essential I think. Unless someone disagrees, keep
posting to this thread and I'll make a commit crediting you as the author.

Thanks,
João



On Wed, Oct 4, 2017 at 2:41 PM, Lele Gaifax <lele@metapensiero.it> wrote:

> Will make a proper bug report with a patch, if you prefer.
>
>     diff --git a/doc/misc/flymake.texi b/doc/misc/flymake.texi
>     index 5dd72f81e2..18d9d05e62 100644
>     --- a/doc/misc/flymake.texi
>     +++ b/doc/misc/flymake.texi
>     @@ -182,7 +182,7 @@ Syntax check statuses
>      @cindex Syntax check statuses
>
>      After syntax check is finished, its status is displayed in the mode
> line.
>     -The following statuses are defined.
>     +The following statuses are defined:
>
>      @multitable @columnfractions 0.25 0.75
>      @item @code{Wait}
>     @@ -356,7 +356,7 @@ Adding support for a new syntax check tool
>      @code{init-function} is required to initialize the syntax check,
>      usually by creating a temporary copy of the buffer contents.  The
>      function must return @code{(list cmd-name arg-list)}.  If
>     -@code{init-function} returns null, syntax check is aborted, by
>     +@code{init-function} returns null, syntax check is aborted, but
>      @code{flymake-mode} is not switched off.
>
>      @item cleanup-function
>     diff --git a/lisp/progmodes/flymake.el b/lisp/progmodes/flymake.el
>     index 0b28dc31cf..1e959d884c 100644
>     --- a/lisp/progmodes/flymake.el
>     +++ b/lisp/progmodes/flymake.el
>     @@ -335,7 +335,7 @@ flymake-diagnostic-functions
>      * the remaining arguments are keyword-value pairs in the
>        form (:KEY VALUE :KEY2 VALUE2...).  Currently, Flymake provides
>        no such arguments, but backend functions must be prepared to
>     -  accept to accept and possibly ignore any number of them.
>     +  accept and possibly ignore any number of them.
>
>      Backend functions are expected to initiate the buffer check, but
>      aren't required to complete it check before exiting: if the
>
> ciao, lele.
> --
> nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
> real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
> lele@metapensiero.it  |                 -- Fortunato Depero, 1929.
>
>
>


-- 
João Távora