Menu

#414 &#$(*&$(* doesn't time out when pdflatex is confused and asking what to do?

workingwiki
open
nobody
None
5
2013-09-26
2013-09-25
Lee Worden
No

I think I have an example case, though I fixed it, I can put the problem back in again.

Discussion

  • Jonathan Dushoff

    Not really following. But if at all possible, we should tell pdflatex to run-always or crash-always. 3-minute timeouts are extremely disruptive to workflow (not least because people almost always decide something else is going on before the timeout comes).

     
  • Lee Worden

    Lee Worden - 2013-09-26

    Not really following you :)

    Do you mean I should use certain command line arguments to stop pdflatex from ever prompting? I'd love to do that... is there an argument for that?

     
  • Jonathan Dushoff

    I'm so confused. Do you also see a bunch of gobbledygook in the subject head?

    interaction=nonstopmode is supposed to stop pdflatex from stopping, if you know what I mean. But that already seems to be the wiki default:

    :::make
    LATEXFLAGS = -interaction=nonstopmode
    

    Are you getting this #414 &#$(*&$( stopping problem when using nonstopmode? You could try using batchmode instead, but I think that just produces less output. How are you getting it to stop?

     
  • Lee Worden

    Lee Worden - 2013-09-26

    On 09/26/2013 03:24 PM, Jonathan Dushoff wrote:

    I'm so confused. Do you also see a bunch of gobbledygook in the subject
    head?

    Yes, it's a comic-book style swear word

    interaction=nonstopmode is /supposed/ to stop pdflatex from stopping, if
    you know what I mean. But that already seems to be the wiki default:

    LATEXFLAGS = -interaction=nonstopmode

    Yes, it is

    Are you getting this #414 &#$(*&$( stopping problem when using
    nonstopmode? You could /try/ using batchmode instead, but I think that
    just produces less output. How are you getting it to stop?

    Presumably it's while using nonstopmode, yes.

    I got it to stop by running top on each cluster node until I figured out
    what to kill manually. :(

    So this ticket is basically a note to myself to go back and find out how
    that happened and how to make sure it never happens again.

     
  • Jonathan Dushoff

    Thanks for explaining. I meant: how did you get pdflatex to stop in the middle of nonstopmode, not how do you get it to stop stopping :-).

     
  • Lee Worden

    Lee Worden - 2013-09-27

    On 09/26/2013 04:56 PM, Jonathan Dushoff wrote:

    Thanks for explaining. I meant: how did you get pdflatex to stop in the
    middle of nonstopmode, not how do you get it to stop stopping :-).

    Aha, a very relevant question. I didn't stop to figure that out,
    because I was rushing to a deadline, but I think I'll be able to
    reconstruct it. Tikz was involved.

     

Anonymous
Anonymous

Add attachments
Cancel