Re: [AUCTeX] debugging of multifile documents with TeX-next-error (2)

[Ralf Angeli]

* Stefan Vollmar (2007-07-03) writes:

> Sorry about the missing logs (but you have to admit I am getting  
> better with my bug reports)

If you progress like this we might be able to give you the yellow belt
in bug reporting soon. (c:

>> then jump to the first error with `C-c `'
>
> this does not work well on my German keyboard, so I have put this  
> line into my .emacs file:
>
> (global-set-key [f6] 'TeX-next-error)

With Emacs 22 you can also use `M-g n'.

> Remember: I am a "rookie" with this - maybe this is the problem (I  
> repeatedly pressed f6 to display the error positions) - altough I do  
> not think so.

I don't think this is the problem either.

> Not in my case: I tried to replicate exactly that scenario and only  
> the error in vhist_spec0.tex is displayed that way.

I could reproduce the problem with your log file.  In the log file there
is the following text:

--8<---------------cut here---------------start------------->8---
! pdfTeX warning (ext4): destination with the same identifier (name{page.1}) ha
s been already used, duplicate ignored
<to be read again> 
                   \penalty 
l.5 \include{vhist_toc}
                        [1] (./vhist_intro.tex
! Undefined control sequence.
l.14 \rwar
          {this-is-an-undefined-macro-into}
) [2] (./vhist_spec0.tex
--8<---------------cut here---------------end--------------->8---

When searching for the first error, the parser finds the warning
starting with "!" and then tries to get line number and context.  In the
context the line with "[1] (./vhist_intro.tex" is included.
(Cf. contents of the *TeX help* buffer.)  So when searching for the next
error, this line, indicating the file where the error is located, is not
included anymore and after the error in the next line starting with "!"
is found, this information is missing.  That's why the wrong file is
displayed.

It is not easy to fix this kind of problem in the parser.  So I suggest
you get rid of the pdfTeX warning or configure your TeX system to
produce file:line:error messages.  I cannot check if this will work
since I cannot reproduce the problem.  In my case (pdfTeXk, Version
3.141592-1.40.3 (Web2C 7.5.6)) the pdfTeX warning does not start with an
exclamation mark.

-- 
Ralf