On 8/26/07, Jushan Bai <[EMAIL PROTECTED]> wrote:

> Thanks for the quick reply.  Quickfix recognizes the errors and is able to 
> detect the location of errors, it sounds odd that it cannot deduce the file 
> name that is being compiled?

LaTeX-suite uses the errorformat variable to define how vim processes
the latex output. Although the command is set within the latexsuite
files, it is based on the example in the help files.

  :help errorformat-LaTeX

Here is what happens. Vim scans the latex output looking for a
filename, then keeps scanning for errors within that filename. It
switches filenames when a new filename is found or when it finds
something that indicates it is no longer processing the current file.
For example, when vim encounters a line of the form

  (filename.tex

it adds filename.tex to its stack of directories, and certain
conditions trigger vim to remove the last file from a stack of
directories. For example, whenever a line with a solitary ) is
processed.

In the following excerpt from a logfile sent to me by Jushan offlist,
ivnote.tex is added to the directory stack on line 1 and it is removed
on the last line. But it should not be.

(ivnote.tex
LaTeX2e <2005/12/01>
Babel <v3.8g> and hyph ...
rman, ngerman, french, loaded.
("F:\Program Files\MiKTeX 2.5\tex\latex\base\article.cls"
Document Class: article 2005/09/16 v1.4f Standard LaTeX document class
("F:\Program Files\MiKTeX 2.5\tex\latex\base\size12.clo"
File: size12.clo 2005/09/16 v1.4f Standard LaTeX file (size option)
)

>From what I can tell, it's not easy to detect when I file is no longer
being processed, so there are errors in constructing the appropriate
directory stack.

One way to fix this would be to fix latex so that its output is
standardized. Maybe a script to post-process the logfile into
something that vim's errorformat can deal with.

Any suggestions?

Franco

--

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Reply via email to