Mercurial > vim
view runtime/tools/mve.txt @ 17555:c2eb5118ba89 v8.1.1775
patch 8.1.1775: error message may be empty in filetype test
commit https://github.com/vim/vim/commit/eee9f65b2a213e9031f172d9d3b22adad6cb985d
Author: Bram Moolenaar <Bram@vim.org>
Date: Mon Jul 29 21:14:42 2019 +0200
patch 8.1.1775: error message may be empty in filetype test
Problem: Error message may be empty in filetype test.
Solution: Use v:exception instead. (Daniel Hahler, closs https://github.com/vim/vim/issues/4744)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Mon, 29 Jul 2019 21:15:08 +0200 |
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.