Mercurial > vim
view runtime/tools/mve.txt @ 19151:f12eda320c78 v8.2.0135
patch 8.2.0135: bracketed paste can still cause invalid memory access
Commit: https://github.com/vim/vim/commit/fe4bbac1166f2e4e3fa18cb966ec7305198c8176
Author: Bram Moolenaar <Bram@vim.org>
Date: Mon Jan 20 21:12:20 2020 +0100
patch 8.2.0135: bracketed paste can still cause invalid memory access
Problem: Bracketed paste can still cause invalid memory access. (Dominique
Pelle)
Solution: Check for NULL pointer.
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Mon, 20 Jan 2020 21:15: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.