Mercurial > vim
view runtime/tools/efm_filter.txt @ 20480:d0bf39eb2b07 v8.2.0794
patch 8.2.0794: libvterm code lags behind the upstream version
Commit: https://github.com/vim/vim/commit/d098b824c10cc20dc55e18c22c4991f61826006e
Author: Bram Moolenaar <Bram@vim.org>
Date: Mon May 18 21:12:59 2020 +0200
patch 8.2.0794: libvterm code lags behind the upstream version
Problem: Libvterm code lags behind the upstream version.
Solution: Include revisions 743 - 747.
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Mon, 18 May 2020 21:15:04 +0200 |
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