On Tue, 2 Dec 2003, Adam R. B. Jack <[EMAIL PROTECTED]> wrote: > Leo Simons" <[EMAIL PROTECTED]: wrote:
>> http://ant.apache.org/manual/listeners.html > > Yup, I knew they exists .. but not if they made it easier. ;-) Depends on the compiler. If compilation errors go to a different stream than warnings (and normal output), you'll get results with different log levels. > Hmm, how do IDEs and such do these things? regular expressions working on stdout/err. This here is what I use in my .xemacs/init.el (indirectly): (setq compilation-error-regexp-alist (append (list ;; works for jikes '("^\\s-*\\[[^]]*\\]\\s-*\\(.+\\):\\([0-9]+\\):\\([0-9]+\\):[0-9]+:[0-9]+:" 1 2 3) ;; works for checkstyle '("^\\s-*\\[[^]]*\\]\\s-*\\(.+\\):\\([0-9]+\\):\\([0-9]+\\):" 1 2 3) ;; works for javac ;; thanks to Barrie Treloar <[EMAIL PROTECTED]> '("^\\s-*\\[[^]]*\\]\\s-*\\(.+\\):\\([0-9]+\\):" 1 2)) compilation-error-regexp-alist)) for the combination of XEmacs, JDEE and Ant. These regexpes should work for the standard logger and could be translated to Python rather easily, I guess. Match 1 is the filename and 2 the line number (3, if present, the column). Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
