This is not really an answer to your question, but an alternate solution I use myself. Personally I find the errorformat system too complicated, and instead use a common very simple errorformat fed by the output of a real function, that I pipe the output of my make command through. I use this: "%f\ %l\ %c\ %m".
I write these error parsing functions in python, but any of the supported scripting languages should do, or even vimL. The logic of this being that such a function is much easier to debug, usable outside of vim, and (at least for me) quicker to write than crafting an errorformat string.
That sounds reasonable. I stumbled upon the error type when I was playing around with ctags -x --c-kinds=f to get a list of all functions into the quickfix buffer for easy viewing and jumping to them in the file I'm currently visiting. Of course the next thing I was trying was to get all interesting things/tags listed in quickfix and some small identifier to distinguish macros, functions, variables, etc.And the error type looked like a good try... – Andreas F.
Dec 10 '10 at 16:40.
It tells the quickfix buffer what type of error a match is (error, warning, or informational). The quickfix buffer will then show that information after the line number and highlight it in a different color. For example, here is a warning and an error: hosts.
Cfg|3473 error| Could not add object property hosts. Cfg|3790 warning| Duplicate definition found for host 'mailgateway' In the quickfix window the word "warning" is in yellow and the word "error" is white on red.In my errorformat I am using %t where the E or W would be in Error or Warning. For example: %trror: %m in file '%f' on line %l.
I have found the following example in quickfix. Txt where %t is used. Examples The format of the file from the Amiga Aztec compiler is: filename>linenumber:columnnumber:errortype:errornumber:errormessage filename name of the file in which the error was detected linenumber line number where the error was detected columnnumber column number where the error was detected errortype type of the error, normally a single 'E' or 'W' errornumber number of the error (for lookup in the manual) errormessage description of the error This can be matched with this errorformat entry: %f>%l:%c:%t:%n:%m It seems that some compiler are storing the error type in a single character E or W, presumably for Error and Warning.
Keep in mind that it is a single character, so it won't match "Warning" or "Error". %t error type (finds a single character).
– Andreas F. Dec 10 '10 at 16:37 I just had a quicklook in Vim source in . /src/quickfix.
C where errorformat are dealt with. I don't exactly see the point of errortype. (Apparently it is always 1 when using the :helpgrep but beyond that...) – Xavier T.
Dec 13 '10 at 9:21 You can have a look there : code.google.Com/p/vim/source/browse/src/quickfix. C The error type is stored in the error list but does not seem to be of much use... – Xavier T. Dec 13 '10 at 18:45.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.