Take the 2-minute tour ×
TeX - LaTeX Stack Exchange is a question and answer site for users of TeX, LaTeX, ConTeXt, and related typesetting systems. It's 100% free, no registration required.

We are successfully using LaTeX at our company to create our product documentation. We have a custom document class that works OK and we currently use TeXnicCenter to edit our documentation. "We" are a bunch of Windows C++ developers.

I'm involved in maintaining our doc creation process and would like to improve the situation for all here when errors and warnings appear during PDF generation from our LaTeX files. We would obviously like to have warning-free "builds" of our documents.

The problem with TeXnicCenter is that it does not parse the pdflatex output and so it's extremely tedious to manually scroll through pages and pages of output to see where a certain error or warning occurred. though it does parse the output and allow to jump to errors and warnings (via toolbar buttons) in the result log, it is not possible to jump to the file position where the error occurred, so it is left to the user to read the warning prelude and conclude where, in which file, the error happened, go there manually and see if he can spot the error.

I have tried TeXmaker and it does a semi decent job at parsing the output but it seems it gets lost as soon as there are errors in addition to warnings.

So long story short what I need is

  • IDE/Editor for Windows + MikTeX
  • One click generation of PDF
  • Resulting in a list/table of warnings and errors and info messages that the developer can click on (as far as possible) to jump to the line where the error occured.
share|improve this question
    
Isn't this a [big-list] qn? –  Charles Stewart Aug 30 '10 at 13:22
    
@Charles: Maybe. Maybe it's too specific (windows, PDF etc.). –  Martin Aug 31 '10 at 13:16
    
oops... my answer doesn't make sense... but the texniccenter i'm using parses my pdflatex logs just fine... –  Mica Dec 17 '10 at 22:26

6 Answers 6

I have only used it for about 10 minutes, but the TeXlipse plugin to Eclipse seems to do a good job of parsing errors and warnings. Here is a screenshot of its error handling taken from their website: TeXlipse's error handling.

share|improve this answer

AUCTeX mode for Emacs can pretty much do all of this, and can display equations, etc., in the .tex file, which can make editing a lot easier. Typing C-c ` after compilation fails will bring the cursor to the spot of the first error.

http://www.gnu.org/software/auctex/

share|improve this answer

Texmaker and TeXstudio, although I've never used either in Windows.

share|improve this answer
    
Could you elaborate a bit on what it's like and why it's good in these editors? Perhaps a screenshot would be good, too. –  doncherry Apr 7 '12 at 11:02

I'm a huge fan of TexNicCenter's log parsing: at the end of the latex run, it totals the number of warnings, errors, bad boxes, etc and displays it. You can then use the next and previous error buttons to jump to the next and previous errors in the log file.

I generally author in emacs + auctex, then compile and debug in texniccenter.

share|improve this answer
1  
somehow I missed the author's paragraph about texniccenter, but my version of texniccenter works fine for parsing my pdflatex logs with the next and previous error buttons. Maybe the author just doesn't have that tool pallet in his texniccenter? –  Mica Dec 17 '10 at 22:28
    
Thanks for pointing out the toolbar buttons for jumping to the next error! I had missed them up to now. (Probably because they are somewhat disjoint from the result pane where the errors are displayed.) –  Martin Dec 20 '10 at 7:50
    
Note, I have since updated the question with your info. How do you solve the problem that you can jump to the errors, but then you don't know where the error is located exactly? –  Martin Apr 7 '12 at 11:45

I always found that WinEdt was pretty good at this. My current editor-of-choice is TeXworks, which currently is not so hot on automated parsing of the log, but the way I work means this is not a big issue for me: I always halt on the first error and jump to the appropriate line number.

share|improve this answer
    
Can you maybe post a link on how to tell pdftex to stop at the first error. –  Martin Aug 29 '10 at 13:36
    
Another vote for WinEDT. –  wishihadabettername Sep 6 '10 at 19:43

Kile, without any doubts. While it is the default LaTeX editor on KDE (a Linux Desktop Environment), according to this link it can also run natively on Windows (installation instructions on that link).

Here is a screenshot from its home page. As you can see, the errors warnings and bad boxes are shown below very clearly. It has keyboard short-cuts for compilation, even to compile just the environment in which you are working at a moment, with a preview in the same window, and lots of other features since its development began more than eight years ago.

Kile screenshot showing some badboxes and errors from the PDFLaTeX output

Give it a try, you will not regret it.

PS: of course the warnings and errors are linked to the line where it occurs.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.