On 11/04/09 00:45, Yue Wu wrote:
[...]
> It's right that vim must use the filename, line, column to jump to the
> match, but I think it can hide these relevant infos from error window,
> just use them transparently. That's the use of errorformat I thought, but
> I failed...
>
IIUC, the 'errorformat' is not meant to tell Vim how to _display_ the
lines of the errorlist but how to _interpret_ them. If there were only
vimgrep, no 'errorformat' would be necessary, but there are a lot of
different compilers for a lot of different languages, and each of them
has different customs about how to display the directory, the file, the
line and the column. The 'errorformat' option tells Vim how to interpret
the output of the current compiler, and translate it from human-readable
to machine-readable: how to extract the directory, filename, line and
column from lines which may or may not be on the same line, while the
match may or may not be included at all in the compiler output, and use
all that info to display (in a different window) the source file with
the cursor as near to the error (or the grep match) as Vim can place it.
All the quickfix commands were (IIUC) originally developed to aid users
in the compile - fix - recompile cycle, and (IIUC) grep, helpgrep and
vimgrep were added in that order as three successive afterthoughts, with
the "local list" facilities being added even later.
Best regards,
Tony.
--
FIRST VILLAGER: We have found a witch. May we burn her?
"Monty Python and the Holy Grail" PYTHON (MONTY)
PICTURES LTD
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
