#914 Incorrect log entries when using \includeonly

None
fixed
nobody
None
1
2014-03-23
2014-03-03
No

I split my document and use \include commands in the main tex file.

To reduce compilation times, I use \includeonly to select the current chapter or a subset of chapters.

However, in this case the output parser fails to assign the errors and warnings to the correct file. They are assigned to the main file instead.

The general case (compile everything without \includeonly) works fine (even if I use \includeonly with all chapters).

Discussion

  • Tim Hoffmann

    Tim Hoffmann - 2014-03-03

    Which version of TXS are you using? Please post the log file, so that we can inverstigate where it goes wrong.

     
  • Tim Hoffmann

    Tim Hoffmann - 2014-03-23

    (log file received by mail)

    hg 4335 (215ddda6ae9f) fixes an error with TeX-style file opening/closing (:<+, :<- in the log parser, that caused this. So the given example should work now.

    Note that sometimes, Over/underful boxes may leak out of the file context in the log. For example, when including this file:

    \section{file 2}
    badBoxFile2aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
    \ref{inFile2}
    

    the log output contains

     (./file2.tex
    
    LaTeX Warning: Reference `inFile2' on page 2 undefined on input line 3.
    
    )
    Overfull \hbox (144.28891pt too wide) in paragraph at lines 2--9
    \OT1/cmr/m/n/12 badBoxFile2aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
    aaaaaaaaaaaaaaaaaaaaaaaaaaaa
    

    So the file is closed before the badbox warning is detected. This seems to be a bug or design flaw in the latex log itself. We cannot do anything about this. However, I assume that this is related to a delayed handling of the wrapping and it won't happen with errors or warnings.

     
  • Tim Hoffmann

    Tim Hoffmann - 2014-03-23
    • status: open --> fixed
    • Group: -->
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks