* doc/misc/flymake.texi (Syntax check statuses): Fix multitable continued rows.

diff --git a/doc/misc/ChangeLog b/doc/misc/ChangeLog
index db3bd460055a13ef9f08520fe40f78422eb284f9..0d6e0785c09bd2a6265df15b116af61bfa27ad0c 100644 (file)
--- a/doc/misc/ChangeLog
+++ b/doc/misc/ChangeLog
@@ -1,3 +1,7 @@
+2013-02-22  Glenn Morris  <rgm@gnu.org>
+
+       * flymake.texi (Syntax check statuses): Fix multitable continued rows.
+
 2013-02-08  Aidan Gauland  <aidalgol@no8wireless.co.nz>
 
        * eshell.texi: Fill most of the missing sections.

diff --git a/doc/misc/flymake.texi b/doc/misc/flymake.texi
index 79259a76503a60c3c3587841ab146b41732bdb76..5dedda16ee1008dc95f98b8620edf8f2b4bb4e7e 100644 (file)
--- a/doc/misc/flymake.texi
+++ b/doc/misc/flymake.texi
@@ -210,14 +210,14 @@ The following statuses are defined.
 @multitable @columnfractions 0.25 0.75
 @item Flymake* or Flymake:E/W*
 @tab  Flymake is currently running. For the second case, E/W contains the
-      error and warning count for the previous run.
+error and warning count for the previous run.
 
 @item Flymake
 @tab  Syntax check is not running. Usually this means syntax check was
-      successfully passed (no errors, no warnings). Other possibilities are:
-      syntax check was killed as a result of executing
-      @code{flymake-compile}, or syntax check cannot start as compilation
-      is currently in progress.
+successfully passed (no errors, no warnings). Other possibilities are:
+syntax check was killed as a result of executing
+@code{flymake-compile}, or syntax check cannot start as compilation
+is currently in progress.
 
 @item Flymake:E/W
 @tab  Number of errors/warnings found by the syntax check process.
@@ -232,9 +232,9 @@ OFF for the buffer.
 @multitable @columnfractions 0.25 0.75
 @item CFGERR
 @tab  Syntax check process returned nonzero exit code, but no
-      errors/warnings were reported. This indicates a possible configuration
-      error (for example, no suitable error message patterns for the
-      syntax check tool).
+errors/warnings were reported. This indicates a possible configuration
+error (for example, no suitable error message patterns for the
+syntax check tool).
 
 @item NOMASTER
 @tab  Flymake was unable to find master file for the current buffer.