Mercurial > vim
view runtime/tools/efm_filter.txt @ 18459:5c0437acebb7 v8.1.2223
patch 8.1.2223: cannot see what buffer an ml_get error is for
Commit: https://github.com/vim/vim/commit/cb86893114ce33dc9c7bd4ff992b05c12406b35d
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat Oct 26 20:56:21 2019 +0200
patch 8.1.2223: cannot see what buffer an ml_get error is for
Problem: Cannot see what buffer an ml_get error is for.
Solution: Add the buffer number and name in the message
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sat, 26 Oct 2019 21:00: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