pdfTeX hangs with this input
up vote
8
down vote
favorite
I know that formula expression is mistyped, but I dont know why pdfTex is frozen(possibly infinite loop) instead of quting nicely? Is there a workaround? Because in case of an erronous input, I need to restart my server.
documentclass{article}
usepackage{graphicx}
usepackage{draftwatermark}
usepackage{breqn}
usepackage{amsmath}
SetWatermarkText{FAST MATH}
SetWatermarkScale{2}
SetWatermarkVerCenter{0.6paperheight}
SetWatermarkAngle{30}
begin{document}
section{Input}
$left. begin{array} { l } { a ) A = { 2 $
section{Solution}
${a: 0}$
end{document}
pdftex
New contributor
|
show 5 more comments
up vote
8
down vote
favorite
I know that formula expression is mistyped, but I dont know why pdfTex is frozen(possibly infinite loop) instead of quting nicely? Is there a workaround? Because in case of an erronous input, I need to restart my server.
documentclass{article}
usepackage{graphicx}
usepackage{draftwatermark}
usepackage{breqn}
usepackage{amsmath}
SetWatermarkText{FAST MATH}
SetWatermarkScale{2}
SetWatermarkVerCenter{0.6paperheight}
SetWatermarkAngle{30}
begin{document}
section{Input}
$left. begin{array} { l } { a ) A = { 2 $
section{Solution}
${a: 0}$
end{document}
pdftex
New contributor
Try running pdflatex with the-halt-on-error
commandline option.
– Eric Marsden
13 hours ago
What do you mean with frozen? Usually it should prompt and wait for input (you will see an asterisk*
on that line). That is to avoid redoing all compilation, but provide a way to "inline edit" the error. The alternative: fix all errors…
– TeXnician
13 hours ago
Btw: you have to loadbreqn
afteramsmath
– DG'
13 hours ago
you can't avoid all loops, setup your server so that it times out if necessary.
– Ulrike Fischer
13 hours ago
1
It seems, in your comments here and to other answers, that your question has more to do with how to handle a condition where a program you're creating/writing has problems when pdflatex hangs due to invalid input; rather than asking what is wrong with the sample input. If so ... you might want to edit this question and its title appropriately to describe what you're really trying to ask. And it may even be the case that this is more appropriately handled elsewhere on Stack Exchange, for example, at Stack Overflow.
– davidbak
9 hours ago
|
show 5 more comments
up vote
8
down vote
favorite
up vote
8
down vote
favorite
I know that formula expression is mistyped, but I dont know why pdfTex is frozen(possibly infinite loop) instead of quting nicely? Is there a workaround? Because in case of an erronous input, I need to restart my server.
documentclass{article}
usepackage{graphicx}
usepackage{draftwatermark}
usepackage{breqn}
usepackage{amsmath}
SetWatermarkText{FAST MATH}
SetWatermarkScale{2}
SetWatermarkVerCenter{0.6paperheight}
SetWatermarkAngle{30}
begin{document}
section{Input}
$left. begin{array} { l } { a ) A = { 2 $
section{Solution}
${a: 0}$
end{document}
pdftex
New contributor
I know that formula expression is mistyped, but I dont know why pdfTex is frozen(possibly infinite loop) instead of quting nicely? Is there a workaround? Because in case of an erronous input, I need to restart my server.
documentclass{article}
usepackage{graphicx}
usepackage{draftwatermark}
usepackage{breqn}
usepackage{amsmath}
SetWatermarkText{FAST MATH}
SetWatermarkScale{2}
SetWatermarkVerCenter{0.6paperheight}
SetWatermarkAngle{30}
begin{document}
section{Input}
$left. begin{array} { l } { a ) A = { 2 $
section{Solution}
${a: 0}$
end{document}
pdftex
pdftex
New contributor
New contributor
edited 13 hours ago
zyy
640613
640613
New contributor
asked 13 hours ago
heral
441
441
New contributor
New contributor
Try running pdflatex with the-halt-on-error
commandline option.
– Eric Marsden
13 hours ago
What do you mean with frozen? Usually it should prompt and wait for input (you will see an asterisk*
on that line). That is to avoid redoing all compilation, but provide a way to "inline edit" the error. The alternative: fix all errors…
– TeXnician
13 hours ago
Btw: you have to loadbreqn
afteramsmath
– DG'
13 hours ago
you can't avoid all loops, setup your server so that it times out if necessary.
– Ulrike Fischer
13 hours ago
1
It seems, in your comments here and to other answers, that your question has more to do with how to handle a condition where a program you're creating/writing has problems when pdflatex hangs due to invalid input; rather than asking what is wrong with the sample input. If so ... you might want to edit this question and its title appropriately to describe what you're really trying to ask. And it may even be the case that this is more appropriately handled elsewhere on Stack Exchange, for example, at Stack Overflow.
– davidbak
9 hours ago
|
show 5 more comments
Try running pdflatex with the-halt-on-error
commandline option.
– Eric Marsden
13 hours ago
What do you mean with frozen? Usually it should prompt and wait for input (you will see an asterisk*
on that line). That is to avoid redoing all compilation, but provide a way to "inline edit" the error. The alternative: fix all errors…
– TeXnician
13 hours ago
Btw: you have to loadbreqn
afteramsmath
– DG'
13 hours ago
you can't avoid all loops, setup your server so that it times out if necessary.
– Ulrike Fischer
13 hours ago
1
It seems, in your comments here and to other answers, that your question has more to do with how to handle a condition where a program you're creating/writing has problems when pdflatex hangs due to invalid input; rather than asking what is wrong with the sample input. If so ... you might want to edit this question and its title appropriately to describe what you're really trying to ask. And it may even be the case that this is more appropriately handled elsewhere on Stack Exchange, for example, at Stack Overflow.
– davidbak
9 hours ago
Try running pdflatex with the
-halt-on-error
commandline option.– Eric Marsden
13 hours ago
Try running pdflatex with the
-halt-on-error
commandline option.– Eric Marsden
13 hours ago
What do you mean with frozen? Usually it should prompt and wait for input (you will see an asterisk
*
on that line). That is to avoid redoing all compilation, but provide a way to "inline edit" the error. The alternative: fix all errors…– TeXnician
13 hours ago
What do you mean with frozen? Usually it should prompt and wait for input (you will see an asterisk
*
on that line). That is to avoid redoing all compilation, but provide a way to "inline edit" the error. The alternative: fix all errors…– TeXnician
13 hours ago
Btw: you have to load
breqn
after amsmath
– DG'
13 hours ago
Btw: you have to load
breqn
after amsmath
– DG'
13 hours ago
you can't avoid all loops, setup your server so that it times out if necessary.
– Ulrike Fischer
13 hours ago
you can't avoid all loops, setup your server so that it times out if necessary.
– Ulrike Fischer
13 hours ago
1
1
It seems, in your comments here and to other answers, that your question has more to do with how to handle a condition where a program you're creating/writing has problems when pdflatex hangs due to invalid input; rather than asking what is wrong with the sample input. If so ... you might want to edit this question and its title appropriately to describe what you're really trying to ask. And it may even be the case that this is more appropriately handled elsewhere on Stack Exchange, for example, at Stack Overflow.
– davidbak
9 hours ago
It seems, in your comments here and to other answers, that your question has more to do with how to handle a condition where a program you're creating/writing has problems when pdflatex hangs due to invalid input; rather than asking what is wrong with the sample input. If so ... you might want to edit this question and its title appropriately to describe what you're really trying to ask. And it may even be the case that this is more appropriately handled elsewhere on Stack Exchange, for example, at Stack Overflow.
– davidbak
9 hours ago
|
show 5 more comments
4 Answers
4
active
oldest
votes
up vote
9
down vote
The issue can be reproduced with a smaller example, showing it has nothing to do with the loaded packages:
documentclass{article}
begin{document}
$left. begin{array} { l } { a ) A = { 2 $
section{Solution}
${a: 0}$
end{document}
The errors in the math formula, followed by the section title, make TeX enter an infinite loop announced by
! LaTeX Error: begin{array} on input line 7 ended by end{document}.
See the LaTeX manual or LaTeX Companion for explanation.
Type H <return> for immediate help.
...
l.12 end{document}
?
! Improper prevdepth.
newpage ...everypar {}fi par ifdim prevdepth
>z@ vskip -ifdim prevd...
l.12 end{document}
The missing end{array}
causes par
to still be defined as “do nothing” like it always is in array
. Since the error recovery here is to try doing end{document}
, LaTeX tries to finish up the page issuing par
, which does nothing.
If we add tracingmacros=1
, after the last error message we see, in the log file after interrupting the program, a string of
par ->
par ->
par ->
par ->
par ->
Solution: don't make silly errors in your input.
Another solution could be running pdflatex
with the option -halt-on-error
, which would stop it at the first error.
However, this is not foolproof. If the user has deffoo{foo}
in their preamble, then the first usage of foo
in the document would start an infinite loop with no error.
1
"Solution: don't make silly errors in your input." unfortuntely this is unavoidable as I explained.
– heral
13 hours ago
add a comment |
up vote
3
down vote
You have unbalanced environments/braces; begin{array}
doesn't have end{array}
and left.
doesn't have right..
. Also, load breqn
after amsmath
and add lmodern
for preventing missing font sizes substitution.
documentclass{article}
usepackage{graphicx,lmodern}
usepackage{draftwatermark}
usepackage{amsmath}
usepackage{breqn}
SetWatermarkText{FAST MATH}
SetWatermarkScale{2}
SetWatermarkVerCenter{0.6paperheight}
SetWatermarkAngle{30}
begin{document}
section{Input}
$ begin{array} { l } a) A = { 2 end{array}$
section{Solution}
${a: 0}$
end{document}
1
I know that there is unbalanced expression in the tex file(there may always be, as some part of it user input), what I need is frozen free pdfTex.
– heral
13 hours ago
add a comment |
up vote
1
down vote
I am not sure of what you are trying to typeset, but please try the following
documentclass{article}
usepackage{graphicx}
usepackage{draftwatermark}
usepackage{amsmath}
SetWatermarkText{FAST MATH}
SetWatermarkScale{0.8}
SetWatermarkVerCenter{0.6paperheight}
SetWatermarkAngle{30}
begin{document}
section{Input}
begin{equation}
left. begin{array}{c}
l \
a \
end{array} right), quad A = { 2
end{equation}
section{Solution}
${a: 0}$
end{document}
Please use compiler XeLaTeX
.
1
Why should you use XeLaTeX for this?
– TeXnician
13 hours ago
add a comment |
up vote
1
down vote
It seems that I am unable to comment on a comment. Weird system or what?
So I am making this into an unsatisfactory answer to your question about the existence of a “workaround” your particular class of “unavoidable silly (or unavoidably silly?) errors”
@heral: (Trying to be nice!) Yes, we are all, well most of us, often silly and we make many errors.
But that is not sufficient reason for there being “workarounds” for all of the silly errrors made by you, and also those made by everyone else.
More technically: It is regrettable that some errors, even some that are non-silly and avoidable, lead to non-space filling recursion (causing an infinite loop or ‘hanging’). There is a theorem somewhere stating that any sufficiently useful software system will provide the possibility of such ‘hanging’ errors and, moreover, that it is impossible to know about and hence trap them all. — no Universal Workarounds! Tough!)
New contributor
Welcome! For the first paragraph look here.
– manooooh
5 hours ago
add a comment |
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
9
down vote
The issue can be reproduced with a smaller example, showing it has nothing to do with the loaded packages:
documentclass{article}
begin{document}
$left. begin{array} { l } { a ) A = { 2 $
section{Solution}
${a: 0}$
end{document}
The errors in the math formula, followed by the section title, make TeX enter an infinite loop announced by
! LaTeX Error: begin{array} on input line 7 ended by end{document}.
See the LaTeX manual or LaTeX Companion for explanation.
Type H <return> for immediate help.
...
l.12 end{document}
?
! Improper prevdepth.
newpage ...everypar {}fi par ifdim prevdepth
>z@ vskip -ifdim prevd...
l.12 end{document}
The missing end{array}
causes par
to still be defined as “do nothing” like it always is in array
. Since the error recovery here is to try doing end{document}
, LaTeX tries to finish up the page issuing par
, which does nothing.
If we add tracingmacros=1
, after the last error message we see, in the log file after interrupting the program, a string of
par ->
par ->
par ->
par ->
par ->
Solution: don't make silly errors in your input.
Another solution could be running pdflatex
with the option -halt-on-error
, which would stop it at the first error.
However, this is not foolproof. If the user has deffoo{foo}
in their preamble, then the first usage of foo
in the document would start an infinite loop with no error.
1
"Solution: don't make silly errors in your input." unfortuntely this is unavoidable as I explained.
– heral
13 hours ago
add a comment |
up vote
9
down vote
The issue can be reproduced with a smaller example, showing it has nothing to do with the loaded packages:
documentclass{article}
begin{document}
$left. begin{array} { l } { a ) A = { 2 $
section{Solution}
${a: 0}$
end{document}
The errors in the math formula, followed by the section title, make TeX enter an infinite loop announced by
! LaTeX Error: begin{array} on input line 7 ended by end{document}.
See the LaTeX manual or LaTeX Companion for explanation.
Type H <return> for immediate help.
...
l.12 end{document}
?
! Improper prevdepth.
newpage ...everypar {}fi par ifdim prevdepth
>z@ vskip -ifdim prevd...
l.12 end{document}
The missing end{array}
causes par
to still be defined as “do nothing” like it always is in array
. Since the error recovery here is to try doing end{document}
, LaTeX tries to finish up the page issuing par
, which does nothing.
If we add tracingmacros=1
, after the last error message we see, in the log file after interrupting the program, a string of
par ->
par ->
par ->
par ->
par ->
Solution: don't make silly errors in your input.
Another solution could be running pdflatex
with the option -halt-on-error
, which would stop it at the first error.
However, this is not foolproof. If the user has deffoo{foo}
in their preamble, then the first usage of foo
in the document would start an infinite loop with no error.
1
"Solution: don't make silly errors in your input." unfortuntely this is unavoidable as I explained.
– heral
13 hours ago
add a comment |
up vote
9
down vote
up vote
9
down vote
The issue can be reproduced with a smaller example, showing it has nothing to do with the loaded packages:
documentclass{article}
begin{document}
$left. begin{array} { l } { a ) A = { 2 $
section{Solution}
${a: 0}$
end{document}
The errors in the math formula, followed by the section title, make TeX enter an infinite loop announced by
! LaTeX Error: begin{array} on input line 7 ended by end{document}.
See the LaTeX manual or LaTeX Companion for explanation.
Type H <return> for immediate help.
...
l.12 end{document}
?
! Improper prevdepth.
newpage ...everypar {}fi par ifdim prevdepth
>z@ vskip -ifdim prevd...
l.12 end{document}
The missing end{array}
causes par
to still be defined as “do nothing” like it always is in array
. Since the error recovery here is to try doing end{document}
, LaTeX tries to finish up the page issuing par
, which does nothing.
If we add tracingmacros=1
, after the last error message we see, in the log file after interrupting the program, a string of
par ->
par ->
par ->
par ->
par ->
Solution: don't make silly errors in your input.
Another solution could be running pdflatex
with the option -halt-on-error
, which would stop it at the first error.
However, this is not foolproof. If the user has deffoo{foo}
in their preamble, then the first usage of foo
in the document would start an infinite loop with no error.
The issue can be reproduced with a smaller example, showing it has nothing to do with the loaded packages:
documentclass{article}
begin{document}
$left. begin{array} { l } { a ) A = { 2 $
section{Solution}
${a: 0}$
end{document}
The errors in the math formula, followed by the section title, make TeX enter an infinite loop announced by
! LaTeX Error: begin{array} on input line 7 ended by end{document}.
See the LaTeX manual or LaTeX Companion for explanation.
Type H <return> for immediate help.
...
l.12 end{document}
?
! Improper prevdepth.
newpage ...everypar {}fi par ifdim prevdepth
>z@ vskip -ifdim prevd...
l.12 end{document}
The missing end{array}
causes par
to still be defined as “do nothing” like it always is in array
. Since the error recovery here is to try doing end{document}
, LaTeX tries to finish up the page issuing par
, which does nothing.
If we add tracingmacros=1
, after the last error message we see, in the log file after interrupting the program, a string of
par ->
par ->
par ->
par ->
par ->
Solution: don't make silly errors in your input.
Another solution could be running pdflatex
with the option -halt-on-error
, which would stop it at the first error.
However, this is not foolproof. If the user has deffoo{foo}
in their preamble, then the first usage of foo
in the document would start an infinite loop with no error.
edited 12 hours ago
answered 13 hours ago
egreg
699k8518583127
699k8518583127
1
"Solution: don't make silly errors in your input." unfortuntely this is unavoidable as I explained.
– heral
13 hours ago
add a comment |
1
"Solution: don't make silly errors in your input." unfortuntely this is unavoidable as I explained.
– heral
13 hours ago
1
1
"Solution: don't make silly errors in your input." unfortuntely this is unavoidable as I explained.
– heral
13 hours ago
"Solution: don't make silly errors in your input." unfortuntely this is unavoidable as I explained.
– heral
13 hours ago
add a comment |
up vote
3
down vote
You have unbalanced environments/braces; begin{array}
doesn't have end{array}
and left.
doesn't have right..
. Also, load breqn
after amsmath
and add lmodern
for preventing missing font sizes substitution.
documentclass{article}
usepackage{graphicx,lmodern}
usepackage{draftwatermark}
usepackage{amsmath}
usepackage{breqn}
SetWatermarkText{FAST MATH}
SetWatermarkScale{2}
SetWatermarkVerCenter{0.6paperheight}
SetWatermarkAngle{30}
begin{document}
section{Input}
$ begin{array} { l } a) A = { 2 end{array}$
section{Solution}
${a: 0}$
end{document}
1
I know that there is unbalanced expression in the tex file(there may always be, as some part of it user input), what I need is frozen free pdfTex.
– heral
13 hours ago
add a comment |
up vote
3
down vote
You have unbalanced environments/braces; begin{array}
doesn't have end{array}
and left.
doesn't have right..
. Also, load breqn
after amsmath
and add lmodern
for preventing missing font sizes substitution.
documentclass{article}
usepackage{graphicx,lmodern}
usepackage{draftwatermark}
usepackage{amsmath}
usepackage{breqn}
SetWatermarkText{FAST MATH}
SetWatermarkScale{2}
SetWatermarkVerCenter{0.6paperheight}
SetWatermarkAngle{30}
begin{document}
section{Input}
$ begin{array} { l } a) A = { 2 end{array}$
section{Solution}
${a: 0}$
end{document}
1
I know that there is unbalanced expression in the tex file(there may always be, as some part of it user input), what I need is frozen free pdfTex.
– heral
13 hours ago
add a comment |
up vote
3
down vote
up vote
3
down vote
You have unbalanced environments/braces; begin{array}
doesn't have end{array}
and left.
doesn't have right..
. Also, load breqn
after amsmath
and add lmodern
for preventing missing font sizes substitution.
documentclass{article}
usepackage{graphicx,lmodern}
usepackage{draftwatermark}
usepackage{amsmath}
usepackage{breqn}
SetWatermarkText{FAST MATH}
SetWatermarkScale{2}
SetWatermarkVerCenter{0.6paperheight}
SetWatermarkAngle{30}
begin{document}
section{Input}
$ begin{array} { l } a) A = { 2 end{array}$
section{Solution}
${a: 0}$
end{document}
You have unbalanced environments/braces; begin{array}
doesn't have end{array}
and left.
doesn't have right..
. Also, load breqn
after amsmath
and add lmodern
for preventing missing font sizes substitution.
documentclass{article}
usepackage{graphicx,lmodern}
usepackage{draftwatermark}
usepackage{amsmath}
usepackage{breqn}
SetWatermarkText{FAST MATH}
SetWatermarkScale{2}
SetWatermarkVerCenter{0.6paperheight}
SetWatermarkAngle{30}
begin{document}
section{Input}
$ begin{array} { l } a) A = { 2 end{array}$
section{Solution}
${a: 0}$
end{document}
answered 13 hours ago
AboAmmar
31k22780
31k22780
1
I know that there is unbalanced expression in the tex file(there may always be, as some part of it user input), what I need is frozen free pdfTex.
– heral
13 hours ago
add a comment |
1
I know that there is unbalanced expression in the tex file(there may always be, as some part of it user input), what I need is frozen free pdfTex.
– heral
13 hours ago
1
1
I know that there is unbalanced expression in the tex file(there may always be, as some part of it user input), what I need is frozen free pdfTex.
– heral
13 hours ago
I know that there is unbalanced expression in the tex file(there may always be, as some part of it user input), what I need is frozen free pdfTex.
– heral
13 hours ago
add a comment |
up vote
1
down vote
I am not sure of what you are trying to typeset, but please try the following
documentclass{article}
usepackage{graphicx}
usepackage{draftwatermark}
usepackage{amsmath}
SetWatermarkText{FAST MATH}
SetWatermarkScale{0.8}
SetWatermarkVerCenter{0.6paperheight}
SetWatermarkAngle{30}
begin{document}
section{Input}
begin{equation}
left. begin{array}{c}
l \
a \
end{array} right), quad A = { 2
end{equation}
section{Solution}
${a: 0}$
end{document}
Please use compiler XeLaTeX
.
1
Why should you use XeLaTeX for this?
– TeXnician
13 hours ago
add a comment |
up vote
1
down vote
I am not sure of what you are trying to typeset, but please try the following
documentclass{article}
usepackage{graphicx}
usepackage{draftwatermark}
usepackage{amsmath}
SetWatermarkText{FAST MATH}
SetWatermarkScale{0.8}
SetWatermarkVerCenter{0.6paperheight}
SetWatermarkAngle{30}
begin{document}
section{Input}
begin{equation}
left. begin{array}{c}
l \
a \
end{array} right), quad A = { 2
end{equation}
section{Solution}
${a: 0}$
end{document}
Please use compiler XeLaTeX
.
1
Why should you use XeLaTeX for this?
– TeXnician
13 hours ago
add a comment |
up vote
1
down vote
up vote
1
down vote
I am not sure of what you are trying to typeset, but please try the following
documentclass{article}
usepackage{graphicx}
usepackage{draftwatermark}
usepackage{amsmath}
SetWatermarkText{FAST MATH}
SetWatermarkScale{0.8}
SetWatermarkVerCenter{0.6paperheight}
SetWatermarkAngle{30}
begin{document}
section{Input}
begin{equation}
left. begin{array}{c}
l \
a \
end{array} right), quad A = { 2
end{equation}
section{Solution}
${a: 0}$
end{document}
Please use compiler XeLaTeX
.
I am not sure of what you are trying to typeset, but please try the following
documentclass{article}
usepackage{graphicx}
usepackage{draftwatermark}
usepackage{amsmath}
SetWatermarkText{FAST MATH}
SetWatermarkScale{0.8}
SetWatermarkVerCenter{0.6paperheight}
SetWatermarkAngle{30}
begin{document}
section{Input}
begin{equation}
left. begin{array}{c}
l \
a \
end{array} right), quad A = { 2
end{equation}
section{Solution}
${a: 0}$
end{document}
Please use compiler XeLaTeX
.
answered 13 hours ago
zyy
640613
640613
1
Why should you use XeLaTeX for this?
– TeXnician
13 hours ago
add a comment |
1
Why should you use XeLaTeX for this?
– TeXnician
13 hours ago
1
1
Why should you use XeLaTeX for this?
– TeXnician
13 hours ago
Why should you use XeLaTeX for this?
– TeXnician
13 hours ago
add a comment |
up vote
1
down vote
It seems that I am unable to comment on a comment. Weird system or what?
So I am making this into an unsatisfactory answer to your question about the existence of a “workaround” your particular class of “unavoidable silly (or unavoidably silly?) errors”
@heral: (Trying to be nice!) Yes, we are all, well most of us, often silly and we make many errors.
But that is not sufficient reason for there being “workarounds” for all of the silly errrors made by you, and also those made by everyone else.
More technically: It is regrettable that some errors, even some that are non-silly and avoidable, lead to non-space filling recursion (causing an infinite loop or ‘hanging’). There is a theorem somewhere stating that any sufficiently useful software system will provide the possibility of such ‘hanging’ errors and, moreover, that it is impossible to know about and hence trap them all. — no Universal Workarounds! Tough!)
New contributor
Welcome! For the first paragraph look here.
– manooooh
5 hours ago
add a comment |
up vote
1
down vote
It seems that I am unable to comment on a comment. Weird system or what?
So I am making this into an unsatisfactory answer to your question about the existence of a “workaround” your particular class of “unavoidable silly (or unavoidably silly?) errors”
@heral: (Trying to be nice!) Yes, we are all, well most of us, often silly and we make many errors.
But that is not sufficient reason for there being “workarounds” for all of the silly errrors made by you, and also those made by everyone else.
More technically: It is regrettable that some errors, even some that are non-silly and avoidable, lead to non-space filling recursion (causing an infinite loop or ‘hanging’). There is a theorem somewhere stating that any sufficiently useful software system will provide the possibility of such ‘hanging’ errors and, moreover, that it is impossible to know about and hence trap them all. — no Universal Workarounds! Tough!)
New contributor
Welcome! For the first paragraph look here.
– manooooh
5 hours ago
add a comment |
up vote
1
down vote
up vote
1
down vote
It seems that I am unable to comment on a comment. Weird system or what?
So I am making this into an unsatisfactory answer to your question about the existence of a “workaround” your particular class of “unavoidable silly (or unavoidably silly?) errors”
@heral: (Trying to be nice!) Yes, we are all, well most of us, often silly and we make many errors.
But that is not sufficient reason for there being “workarounds” for all of the silly errrors made by you, and also those made by everyone else.
More technically: It is regrettable that some errors, even some that are non-silly and avoidable, lead to non-space filling recursion (causing an infinite loop or ‘hanging’). There is a theorem somewhere stating that any sufficiently useful software system will provide the possibility of such ‘hanging’ errors and, moreover, that it is impossible to know about and hence trap them all. — no Universal Workarounds! Tough!)
New contributor
It seems that I am unable to comment on a comment. Weird system or what?
So I am making this into an unsatisfactory answer to your question about the existence of a “workaround” your particular class of “unavoidable silly (or unavoidably silly?) errors”
@heral: (Trying to be nice!) Yes, we are all, well most of us, often silly and we make many errors.
But that is not sufficient reason for there being “workarounds” for all of the silly errrors made by you, and also those made by everyone else.
More technically: It is regrettable that some errors, even some that are non-silly and avoidable, lead to non-space filling recursion (causing an infinite loop or ‘hanging’). There is a theorem somewhere stating that any sufficiently useful software system will provide the possibility of such ‘hanging’ errors and, moreover, that it is impossible to know about and hence trap them all. — no Universal Workarounds! Tough!)
New contributor
New contributor
answered 8 hours ago
PGSan
113
113
New contributor
New contributor
Welcome! For the first paragraph look here.
– manooooh
5 hours ago
add a comment |
Welcome! For the first paragraph look here.
– manooooh
5 hours ago
Welcome! For the first paragraph look here.
– manooooh
5 hours ago
Welcome! For the first paragraph look here.
– manooooh
5 hours ago
add a comment |
heral is a new contributor. Be nice, and check out our Code of Conduct.
heral is a new contributor. Be nice, and check out our Code of Conduct.
heral is a new contributor. Be nice, and check out our Code of Conduct.
heral is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f461319%2fpdftex-hangs-with-this-input%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Try running pdflatex with the
-halt-on-error
commandline option.– Eric Marsden
13 hours ago
What do you mean with frozen? Usually it should prompt and wait for input (you will see an asterisk
*
on that line). That is to avoid redoing all compilation, but provide a way to "inline edit" the error. The alternative: fix all errors…– TeXnician
13 hours ago
Btw: you have to load
breqn
afteramsmath
– DG'
13 hours ago
you can't avoid all loops, setup your server so that it times out if necessary.
– Ulrike Fischer
13 hours ago
1
It seems, in your comments here and to other answers, that your question has more to do with how to handle a condition where a program you're creating/writing has problems when pdflatex hangs due to invalid input; rather than asking what is wrong with the sample input. If so ... you might want to edit this question and its title appropriately to describe what you're really trying to ask. And it may even be the case that this is more appropriately handled elsewhere on Stack Exchange, for example, at Stack Overflow.
– davidbak
9 hours ago