Mercurial > vim
view runtime/tools/mve.txt @ 31069:39698292a849 v9.0.0869
patch 9.0.0869: bogus error when string used after :elseif
Commit: https://github.com/vim/vim/commit/28c56d501352bd98472d23667bade683877cadcc
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat Nov 12 23:12:55 2022 +0000
patch 9.0.0869: bogus error when string used after :elseif
Problem: Bogus error when string used after :elseif.
Solution: Do not consider a double quote the start of a comment.
(closes #11534)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sun, 13 Nov 2022 00:15:03 +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.