Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#264 Latex messeges from main document are parsed incorrectly

closed-fixed
5
2010-01-18
2010-01-12
Alexander Herz
No

I'm running MikTex 2.8.3563 and TexNic alpha build 1071 on vista. Latex messages for any document but the main tex file (so they are \included or similar) are parsed correctly (I can double click them to get to the line which caused the output; the file is displayed in the file column in the error view correctly).
Messeges originating from the main tex file are shown in the error view as well, but no file name is displayed in the file column. this alone would be fine with me, but double clicking on the error spawns a message box saing that "adkljfhadk lsj not found" and does not jump to the correct line. Where "adkljfhadk lsj" is some weird unicode characters I cannot type here.

I've attached the latex log which includes 2 errors, the first one is parsed incorrectly, the second one is parsed correctly.
Related to this: It would be nice if the line latex outputs after an error or warning would be included in the error view as it tells you what went wrong.

Discussion

1 2 3 4 > >> (Page 1 of 4)
  • Sergiu Dotenco
    Sergiu Dotenco
    2010-01-13

    Please provide a TeX document (as small as possible) that allows to reproduce the problem.

     
  • Alexander Herz
    Alexander Herz
    2010-01-13

    The example I uploaded uses two undefined commands: \unkown0 (in the maintex file) and \unkown1 (in the included tex file). The latex error output for \unknown1 is always parsed correctly. The output for \unkown0 is parsed correctly when the document class article is used, if our custom document class is used which defines a few additional commands then the output for \unkown0 is NOT parsed correctly. The additional latex messages produced by our custom doc class can be seen in the log file I uploaded earlier (I don't wonna upload the complete custom document class). Apparently, the latex output produced by our custom doc class confuses texnic's latex log parser.

     
  • Sergiu Dotenco
    Sergiu Dotenco
    2010-01-13

    Here's the problem: TeXnicCenter parses latex console output, not the log file. Try to find out what part of your class is responsible for producing the described behavior, extract that part and provide it as well. You can also send us the class by e-mail if you don't to make it publicly available. Otherwise we can't help you.

     
1 2 3 4 > >> (Page 1 of 4)


Anonymous


Cancel   Add attachments