Mercurial > vim
view runtime/tools/efm_filter.txt @ 23513:872239543313 v8.2.2299
patch 8.2.2299: Vim9: invalid memory access making error message flaky
Commit: https://github.com/vim/vim/commit/d1510ee9469f623c872a18b6e3c3666c0fb23c58
Author: Bram Moolenaar <Bram@vim.org>
Date: Mon Jan 4 16:15:58 2021 +0100
patch 8.2.2299: Vim9: invalid memory access making error message flaky
Problem: Vim9: invalid memory access making error message flaky.
Solution: Do not check cmd_argt for CMD_USER. (issue https://github.com/vim/vim/issues/7467)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Mon, 04 Jan 2021 16:30: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