Mercurial > vim
view runtime/tools/mve.txt @ 10589:b0c9c1a05054 v8.0.0184
patch 8.0.0184: when an error is caught Vim still exits with non-zero result
commit https://github.com/vim/vim/commit/2b7bc567b9238aaac682236cb4f727d0376e1302
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat Jan 14 19:24:52 2017 +0100
patch 8.0.0184: when an error is caught Vim still exits with non-zero result
Problem: When in Ex mode and an error is caught by try-catch, Vim still
exits with a non-zero exit code.
Solution: Don't set ex_exitval when inside a try-catch. (partly by Christian
Brabandt)
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Sat, 14 Jan 2017 19:30: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.