From: Massimiliano Mirra <list@...>
Date: 2002-08-18T20:14:22+09:00
Subject: Re: IDE vs. editor

On Sun, Aug 18, 2002 at 12:05:02PM +0900, Dave Thomas wrote:
> > Thanks to you and Alan for the tip.  A sensible approach.  But I
> > wonder if any output buffer can be forced to be parsed into line
> > anchors to another buffer.  Elisp wizards, hints?
> Use M-x compile to run the tests, 

It's M-x compile'ing that turns me a bit down, because it requires the
extra step of saving.  Right now, I just press C-c-c, current buffer
is evaluated (whether saved or not), and since it contains:

if __FILE__ == $0
  require 'test/unit'
  ...
end

...tests are run, and output shown in a lower window.  I was wondering
whether that appearing window could be made a parsed-for-line-numbers
one like M-x compile's.  Maybe I'm just being too lazy...

> and set compilation-error-regexp-alist to parse out the line number
> and file name of the failing test. Then next-error (normally bound
> to ^X-` will load the file and take you to the line in error. (This
> is all theory: I've never tried parsing Test::Unit output, but I
> can't see a problem doing it.)

(Some minutes later...)

...or maybe I'd better just RTFM. :-)

C-x ` runs the command next-error
   which is an interactive compiled Lisp function in `compile'.
(next-error &optional ARGP)

[...]

C-x ` normally uses the most recently started compilation or
grep buffer.  However, it can operate on any buffer with output from
the M-x compile and M-x grep commands, or, more generally, on any
buffer in Compilation mode or with Compilation Minor mode enabled.  To
specify use of a particular buffer for error messages, type
C-x ` in that buffer.


Ok, time to learn some elisp. :-)


Massimiliano