Mercurial > vim

view runtime/tools/mve.txt @ 7605:8fc60af6dbf5 v7.4.1102

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc Author: Bram Moolenaar <Bram@vim.org> Date: Sat Jan 16 15:40:53 2016 +0100 patch 7.4.1102 Problem: Debugger has no stack backtrace support. Solution: Add "backtrace", "frame", "up" and "down" commands. (Alberto Fanjul, closes https://github.com/vim/vim/issues/433)
author Christian Brabandt <cb@256bit.org>
date Sat, 16 Jan 2016 15:45:04 +0100
parents 3fc0f57ecb91
children
line wrap: on
line source

[ The mve awk script was posted on the vimdev mailing list ]

From: jimmer@barney.mdhc.mdc.com (J. McGlasson)
Date: Mon, 31 Mar 1997 13:16:49 -0700 (Mar)

My compiler (SGI MIPSpro C compiler - IRIX 6.4) works like this.
I have written a script mve (make vim errors), through which I pipe my make
output, which translates output of the following form:

cfe: Error: syntax.c, line 4: Syntax Error
     int i[12;
 ------------^

into:

 cl.c, line 4, col 12 :  Syntax Error

(in vim notation:  %f, line %l, col %c : %m)

You might be able to tailor this for your compiler's output.