From: Carl Parrish <cparrish@...>
Date: 2002-08-18T22:59:13+09:00
Subject: Re: IDE vs. editor

Does anyone know of a good source on best practices to make ruby coding
easier with VIM? I'm looking for tips like these, how to intergrate
Test::Unit in VIM if there are better Syntax files. How to access CVS
from VIM. I"m pretty certain all this is possible I just don't know
where or how. If this source isn't already available I'd be more than
willing to create it. The only problem is I don't know it already.; 

Carl P. 



On Sat, 2002-08-17 at 20:05, Dave Thomas wrote:
> Massimiliano Mirra <list@NOSPAMchromatic-harp.com> writes:
> 
> > On Sun, Aug 18, 2002 at 03:57:22AM +0900, Alan Chen wrote:
> > > > How do you run tests and then jump to offending lines?  I use to run
> > > I've been running my unit tests from a makefile, 
> > 
> > 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, 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.)
> 
> 
> Cheers
> 
> 
> Dave