GNU bug report logs - #4079
23.1.50; compile.el comments for gnu pattern first line

Previous Next

Full log

View this message in rfc822 format

From: Kevin Ryde <user42 <at> zip.com.au>
To: emacs-pretest-bug <at> gnu.org
Subject: bug#4079: 23.1.50; compile.el comments for gnu pattern first line
Date: Sat, 08 Aug 2009 11:16:51 +1000

[Message part 1 (text/plain, inline)]

Answering a question left by Stefan ...

2009-08-08  Kevin Ryde  <user42 <at> zip.com.au>

	* progmodes/compile.el (compilation-error-regexp-alist-alist): Add
	crib to `gnu' pattern on what the first line is for.  (The pattern is
	so hairy some verbosity can be tolerated in the comments!)

[compile.el.gnu-comment.diff (text/x-diff, inline)]

*** compile.el	11 Jul 2009 07:12:48 +1000	1.495
--- compile.el	08 Aug 2009 11:12:37 +1000	
***************
*** 234,240 ****
       (2 (compilation-face '(3))))
  
      (gnu
!      ;; I have no idea what this first line is supposed to match, but it
       ;; makes things ambiguous with output such as "foo:344:50:blabla" since
       ;; the "foo" part can match this first line (in which case the file
       ;; name as "344").  To avoid this, the second line disallows filenames
--- 234,247 ----
       (2 (compilation-face '(3))))
  
      (gnu
!      ;; The first line matches the program name for
!      ;;     PROGRAM:SOURCE-FILE-NAME:LINENO: MESSAGE
!      ;; format as per gnu standards.info "Errors" for non-interactive
!      ;; programs other than compilers.  Eg. the "jade:" entry in
!      ;; compilation.txt
!      ;;     jade:dbcommon.dsl:133:17:E: missing argument for function call
!      ;;
!      ;; The first line
       ;; makes things ambiguous with output such as "foo:344:50:blabla" since
       ;; the "foo" part can match this first line (in which case the file
       ;; name as "344").  To avoid this, the second line disallows filenames

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.