Mercurial > vim
view runtime/tools/efm_filter.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
[adopted from a message that Ives posted in the Vim mailing list] Some compilers produce an error message that cannot be handled with 'errorformat' in Vim. Following is an example of a Perl script that translates one error message into something that Vim understands. The compiler that generates this kind of error messages (4 lines): "/tmp_mnt/cm/src/apertos/MoU/MetaCore/MetaCore/common/src/MetaCoreImp_M.cc", line 50: error(3114): identifier "PRIMITIVE_M" is undefined return(ExecuteCore(PRIMITIVE_M, You can find a small perl program at the end. The way I use it is: :set errorformat=%f>%l:%c:%t:%n:%m :set makeprg=clearmake\ -C\ gnu :set shellpipe=2>&1\|\ vimccparse If somebody thinks this is useful: feel free to do whatever you can think of with this code. -Ives ____________________________________________________________ Ives Aerts (SW Developer) Sony Telecom Europe ives@sonytel.be St.Stevens Woluwestr. 55 `Death could create most things, B-1130 Brussels, Belgium except for plumbing.' PHONE : +32 2 724 19 67 (Soul Music - T.Pratchett) FAX : +32 2 726 26 86