My apologies if this has been asked before — but I searched both on this site and online in general, and I couldn't find a solution to my problem anywhere.

I recently reinstalled MiKTeX 2.9 on one of my computers. When I compile, I have a habit of hitting r for \nonstopmode after the very first error. Previously, after I do that, MiKTeX (or rather pdfLaTex that it runs) would still generate an output pdf file. Of course, the file would look weird, but then I can fix that one error, and compile again, and so on, and so forth …

But now, in this new installation, there's no output produced when I do that. Instead, after doing all the work it eventually stops and shows an error message "Sorry, but "MiKTeX Compiler Driver" did not succeed."

I'm sure there's an option for the compiler that controls this behavior, but I don't know what that option is. Could you help me please?

EDIT: Here's some additional info that maybe could help. In the "Tool Configuration" dialog of the "Typesetting" tab of "TexWorks Preferences", I have the following options for the pdfLaTeX+MakeIndex+BibTeX profile:

  • Your chances to get help with the current level of provided information are very small. In general, I would not recommend having errors in the code as a normal situation. Tip: tex.meta.stackexchange.com/questions/228 – Dr. Manuel Kuehner Mar 6 '18 at 0:43
  • 1
    @Dr.ManuelKuehner: I appreciate your feedback. I'm not a newbie to SE, although I'm mostly active on other SE sites, not here -- I'm only mentioning that to make a point that I know in general what is expected of a good question. But I'm not sure what else would help here. Could you please advise what additional information would help? My question is not about any particular code, but rather about MiKTeX compiler options. – zipirovich Mar 6 '18 at 0:57
  • 1
    I am no expert on compiler options either. Maybe you are in luck and someone around here dealt with a similar issue before. Still, I would provide a small but complete code example with a mistake on purpose. Then show the error message and state your compiler options so that others can reproduce your problem. – Dr. Manuel Kuehner Mar 6 '18 at 1:03
  • 1
    Sometimes, a PDF cannot be produced. So, without a minimal example of a case which demonstrates the problem, we can't know whether this is particular to your setup or specific to your code. If you tell TeX to carry on regardless of errors, it will try to do something by guessing what was intended. Even if it guesses wrong, this sometimes succeeds. But only sometimes. Other times, compilation fails because things are just too screwed up or screwed up in another way. So far, your question includes no evidence that ultimate failure is not the expected behaviour. – cfr Mar 6 '18 at 1:20
  • 2
    The profile you describe probably attempts to execute multiple binaries, but you have not shown the sequence of commands executed. Moreover, you have not said what happens if you run e.g. pdflatex only without trying makeindex/xindy or bibtex/biber. – cfr Mar 6 '18 at 1:24

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.