Mercurial > vim

view runtime/tools/mve.txt @ 13200:017a81187128 v8.0.1474

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 8.0.1474: Visual C 2017 has multiple MSVCVER numbers commit https://github.com/vim/vim/commit/dd08b6a32b639b8c7a11275e04ae0a7ffc43aed0 Author: Bram Moolenaar <Bram@vim.org> Date: Tue Feb 6 22:02:43 2018 +0100 patch 8.0.1474: Visual C 2017 has multiple MSVCVER numbers Problem: Visual C 2017 has multiple MSVCVER numbers. Solution: Assume the 2017 version if MSVCVER >= 1910. (Leonardo Valeri Manera, closes #2619)
author Christian Brabandt <cb@256bit.org>
date Tue, 06 Feb 2018 22:15:05 +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.