rubber hangs because nonstopmode fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Rubber |
Fix Released
|
Low
|
Sebastian Kapfer |
Bug Description
using rubber revision 416
$ rubber -c 'set arguments lol' -f -d beamer.tex
compiling beamer.tex...
rubber hangs. pressing ctrl+d makes rubber continue and print this line
Could not run pdflatex.
invoking rubber with -v shows the problem
$ rubber -v -c 'set arguments lol' -f -d beamer.tex
compiling beamer.tex...
executing: pdflatex l o l \nonstopmode \input{beamer.tex}
again, pressing ctrl+d lets rubber continue with these lines
Could not run pdflatex.
There were errors compiling beamer.tex.
Rubber hangs because pdflatex drops to a prompt because \nonstopmode has not been executed yet.
I think a fix would be to invoke pdflatex (or latex) using the "-interaction nonstopmode" option, or to make sure that /nonstopmode is always at the beginning.
I agree that it is an error to invoke rubber using -c 'set arguments lol', but that error should not cause rubber to hang.
Related branches
Changed in rubber: | |
milestone: | 1.2 → none |
status: | Fix Committed → Fix Released |
A fix has been committed to the trunk branch: Rubber now does not hand subprocesses a handle to stdin, so they cannot block reading from it.