From: Glenn Morris <rgm@gnu.org>
Date: Tue, 16 Dec 2014 03:30:50 +0000 (-0800)
Subject: * test/automated/data/flymake/Makefile: Comment.
X-Git-Tag: emacs-25.0.90~2635^2~58
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=15426191a1353ac208d8ebe4a5920228e0df41a4;p=emacs.git

* test/automated/data/flymake/Makefile: Comment.
---

diff --git a/test/automated/data/flymake/Makefile b/test/automated/data/flymake/Makefile
index a92db78b46f..0f3f39791c8 100644
--- a/test/automated/data/flymake/Makefile
+++ b/test/automated/data/flymake/Makefile
@@ -2,9 +2,11 @@
 
 CC_OPTS = -Wall
 
-## Recent gcc's (e.g. 4.8.2 on RHEL7) can automatically colorize their output,
+## Recent gcc (e.g. 4.8.2 on RHEL7) can automatically colorize their output,
 ## which can confuse flymake.  Set GCC_COLORS to disable that.
-## TODO is this something that should be fixed in flymake?
+## This only seems to be an issue in batch mode, where you would not
+## normally use flymake, so it seems like just avoiding the issue
+## in this test is fine.  Set flymake-log-level to 3 to investigate.
 check-syntax:
 	GCC_COLORS= $(CC) $(CC_OPTS) ${CHK_SOURCES}