Mercurial > vim
view runtime/tools/mve.txt @ 27970:212c5894b8b1 v8.2.4510
patch 8.2.4510: Vim9: shortening commands leads to confusing script
Commit: https://github.com/vim/vim/commit/204852ae2adfdde10c656ca7f14e5b4207a69172
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat Mar 5 12:56:44 2022 +0000
patch 8.2.4510: Vim9: shortening commands leads to confusing script
Problem: Vim9: shortening commands leads to confusing script.
Solution: In Vim9 script require at least ":cont" for ":continue", "const"
instead of "cons", "break" instead of "brea", "catch" instead of
"cat", "else" instead of "el" "elseif" instead of "elsei" "endfor"
instead of "endfo" "endif" instead of "en" "endtry" instead of
"endt", "finally" instead of "fina", "throw" instead of "th",
"while" instead of "wh".
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sat, 05 Mar 2022 14:00: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.