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).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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).
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?
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:
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?
On 09/26/2013 03:24 PM, Jonathan Dushoff wrote:
Yes, it's a comic-book style swear word
Yes, it is
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.
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 :-).
On 09/26/2013 04:56 PM, Jonathan Dushoff wrote:
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.