aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChong Yidong2009-08-10 02:44:58 +0000
committerChong Yidong2009-08-10 02:44:58 +0000
commit6807d8ca512a3516df3e56e185204f2845bc121e (patch)
tree0db6466b9befeead70eeef9844640c89e87f6a6c
parent77437343067af467cab2c8925d2e86a769701feb (diff)
downloademacs-6807d8ca512a3516df3e56e185204f2845bc121e.tar.gz
emacs-6807d8ca512a3516df3e56e185204f2845bc121e.zip
Update comment (from Kevin Ryde).
-rw-r--r--lisp/progmodes/compile.el18
1 files changed, 13 insertions, 5 deletions
diff --git a/lisp/progmodes/compile.el b/lisp/progmodes/compile.el
index cad19b70674..6249f50cc9c 100644
--- a/lisp/progmodes/compile.el
+++ b/lisp/progmodes/compile.el
@@ -234,11 +234,19 @@ of[ \t]+\"?\\([a-zA-Z]?:?[^\":\n]+\\)\"?:" 3 2 nil (1))
234 (2 (compilation-face '(3)))) 234 (2 (compilation-face '(3))))
235 235
236 (gnu 236 (gnu
237 ;; I have no idea what this first line is supposed to match, but it 237 ;; The first line matches the program name for
238 ;; makes things ambiguous with output such as "foo:344:50:blabla" since 238
239 ;; the "foo" part can match this first line (in which case the file 239 ;; PROGRAM:SOURCE-FILE-NAME:LINENO: MESSAGE
240 ;; name as "344"). To avoid this, the second line disallows filenames 240
241 ;; exclusively composed of digits. --Stef 241 ;; format, which is used for non-interactive programs other than
242 ;; compilers (e.g. the "jade:" entry in compilation.txt).
243
244 ;; This first line makes things ambiguous with output such as
245 ;; "foo:344:50:blabla" since the "foo" part can match this first
246 ;; line (in which case the file name as "344"). To avoid this,
247 ;; the second line disallows filenames exclusively composed of
248 ;; digits.
249
242 ;; Similarly, we get lots of false positives with messages including 250 ;; Similarly, we get lots of false positives with messages including
243 ;; times of the form "HH:MM:SS" where MM is taken as a line number, so 251 ;; times of the form "HH:MM:SS" where MM is taken as a line number, so
244 ;; the last line tries to rule out message where the info after the 252 ;; the last line tries to rule out message where the info after the