Mercurial > vim
view runtime/tools/efm_filter.txt @ 19587:e61dc51ab9b4 v8.2.0350
patch 8.2.0350: Vim9: expression tests don't use recognized constants
Commit: https://github.com/vim/vim/commit/080457c02d51f87e7d61ebd3e3aeef4468be939c
Author: Bram Moolenaar <Bram@vim.org>
Date: Tue Mar 3 21:53:32 2020 +0100
patch 8.2.0350: Vim9: expression tests don't use recognized constants
Problem: Vim9: expression tests don't use recognized constants.
Solution: Recognize "true" and "false" as constants. Make skipping work for
assignment and expression evaluation.
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Tue, 03 Mar 2020 22:00:04 +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