pdfTeX hangs with this input











up vote
11
down vote

favorite
2












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}









share|improve this question









New contributor




heral is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • Try running pdflatex with the -halt-on-error commandline option.
    – Eric Marsden
    yesterday






  • 2




    you can't avoid all loops, setup your server so that it times out if necessary.
    – Ulrike Fischer
    yesterday






  • 3




    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
    yesterday






  • 3




    You might be interested in Using module 'subprocess' with timeout to timeout a process called from python. If you're allowing arbitrary unchecked code in your document, I hope you have your TeX installation set up with the highest security settings.
    – Nicola Talbot
    yesterday






  • 4




    @heral it is provably impossible in any non trivial programming language to avoid or detect all loops. This is the "Turing halting problem", the halt on error suggestion will stop tex if there is an error but it is easy to make tex loop in non-error cases, deffoo{foo}foo for example.
    – David Carlisle
    yesterday















up vote
11
down vote

favorite
2












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}









share|improve this question









New contributor




heral is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • Try running pdflatex with the -halt-on-error commandline option.
    – Eric Marsden
    yesterday






  • 2




    you can't avoid all loops, setup your server so that it times out if necessary.
    – Ulrike Fischer
    yesterday






  • 3




    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
    yesterday






  • 3




    You might be interested in Using module 'subprocess' with timeout to timeout a process called from python. If you're allowing arbitrary unchecked code in your document, I hope you have your TeX installation set up with the highest security settings.
    – Nicola Talbot
    yesterday






  • 4




    @heral it is provably impossible in any non trivial programming language to avoid or detect all loops. This is the "Turing halting problem", the halt on error suggestion will stop tex if there is an error but it is easy to make tex loop in non-error cases, deffoo{foo}foo for example.
    – David Carlisle
    yesterday













up vote
11
down vote

favorite
2









up vote
11
down vote

favorite
2






2





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}









share|improve this question









New contributor




heral is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











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}






errors






share|improve this question









New contributor




heral is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




heral is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 15 hours ago









Martin Schröder

12.7k638120




12.7k638120






New contributor




heral is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked yesterday









heral

592




592




New contributor




heral is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





heral is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






heral is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • Try running pdflatex with the -halt-on-error commandline option.
    – Eric Marsden
    yesterday






  • 2




    you can't avoid all loops, setup your server so that it times out if necessary.
    – Ulrike Fischer
    yesterday






  • 3




    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
    yesterday






  • 3




    You might be interested in Using module 'subprocess' with timeout to timeout a process called from python. If you're allowing arbitrary unchecked code in your document, I hope you have your TeX installation set up with the highest security settings.
    – Nicola Talbot
    yesterday






  • 4




    @heral it is provably impossible in any non trivial programming language to avoid or detect all loops. This is the "Turing halting problem", the halt on error suggestion will stop tex if there is an error but it is easy to make tex loop in non-error cases, deffoo{foo}foo for example.
    – David Carlisle
    yesterday


















  • Try running pdflatex with the -halt-on-error commandline option.
    – Eric Marsden
    yesterday






  • 2




    you can't avoid all loops, setup your server so that it times out if necessary.
    – Ulrike Fischer
    yesterday






  • 3




    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
    yesterday






  • 3




    You might be interested in Using module 'subprocess' with timeout to timeout a process called from python. If you're allowing arbitrary unchecked code in your document, I hope you have your TeX installation set up with the highest security settings.
    – Nicola Talbot
    yesterday






  • 4




    @heral it is provably impossible in any non trivial programming language to avoid or detect all loops. This is the "Turing halting problem", the halt on error suggestion will stop tex if there is an error but it is easy to make tex loop in non-error cases, deffoo{foo}foo for example.
    – David Carlisle
    yesterday
















Try running pdflatex with the -halt-on-error commandline option.
– Eric Marsden
yesterday




Try running pdflatex with the -halt-on-error commandline option.
– Eric Marsden
yesterday




2




2




you can't avoid all loops, setup your server so that it times out if necessary.
– Ulrike Fischer
yesterday




you can't avoid all loops, setup your server so that it times out if necessary.
– Ulrike Fischer
yesterday




3




3




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
yesterday




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
yesterday




3




3




You might be interested in Using module 'subprocess' with timeout to timeout a process called from python. If you're allowing arbitrary unchecked code in your document, I hope you have your TeX installation set up with the highest security settings.
– Nicola Talbot
yesterday




You might be interested in Using module 'subprocess' with timeout to timeout a process called from python. If you're allowing arbitrary unchecked code in your document, I hope you have your TeX installation set up with the highest security settings.
– Nicola Talbot
yesterday




4




4




@heral it is provably impossible in any non trivial programming language to avoid or detect all loops. This is the "Turing halting problem", the halt on error suggestion will stop tex if there is an error but it is easy to make tex loop in non-error cases, deffoo{foo}foo for example.
– David Carlisle
yesterday




@heral it is provably impossible in any non trivial programming language to avoid or detect all loops. This is the "Turing halting problem", the halt on error suggestion will stop tex if there is an error but it is easy to make tex loop in non-error cases, deffoo{foo}foo for example.
– David Carlisle
yesterday










4 Answers
4






active

oldest

votes

















up vote
13
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.






share|improve this answer



















  • 1




    "Solution: don't make silly errors in your input." unfortuntely this is unavoidable as I explained.
    – heral
    yesterday


















up vote
4
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}





share|improve this answer

















  • 2




    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
    yesterday


















up vote
0
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.






share|improve this answer

















  • 3




    Why should you use XeLaTeX for this?
    – TeXnician
    yesterday


















up vote
0
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!)






share|improve this answer








New contributor




PGSan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.














  • 2




    Welcome! For the first paragraph look here.
    – manooooh
    yesterday













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






heral is a new contributor. Be nice, and check out our Code of Conduct.










 

draft saved


draft discarded


















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

























4 Answers
4






active

oldest

votes








4 Answers
4






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
13
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.






share|improve this answer



















  • 1




    "Solution: don't make silly errors in your input." unfortuntely this is unavoidable as I explained.
    – heral
    yesterday















up vote
13
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.






share|improve this answer



















  • 1




    "Solution: don't make silly errors in your input." unfortuntely this is unavoidable as I explained.
    – heral
    yesterday













up vote
13
down vote










up vote
13
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.






share|improve this answer














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.







share|improve this answer














share|improve this answer



share|improve this answer








edited yesterday

























answered yesterday









egreg

699k8518593130




699k8518593130








  • 1




    "Solution: don't make silly errors in your input." unfortuntely this is unavoidable as I explained.
    – heral
    yesterday














  • 1




    "Solution: don't make silly errors in your input." unfortuntely this is unavoidable as I explained.
    – heral
    yesterday








1




1




"Solution: don't make silly errors in your input." unfortuntely this is unavoidable as I explained.
– heral
yesterday




"Solution: don't make silly errors in your input." unfortuntely this is unavoidable as I explained.
– heral
yesterday










up vote
4
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}





share|improve this answer

















  • 2




    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
    yesterday















up vote
4
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}





share|improve this answer

















  • 2




    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
    yesterday













up vote
4
down vote










up vote
4
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}





share|improve this answer












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}






share|improve this answer












share|improve this answer



share|improve this answer










answered yesterday









AboAmmar

31.1k22780




31.1k22780








  • 2




    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
    yesterday














  • 2




    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
    yesterday








2




2




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
yesterday




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
yesterday










up vote
0
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.






share|improve this answer

















  • 3




    Why should you use XeLaTeX for this?
    – TeXnician
    yesterday















up vote
0
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.






share|improve this answer

















  • 3




    Why should you use XeLaTeX for this?
    – TeXnician
    yesterday













up vote
0
down vote










up vote
0
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.






share|improve this answer












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.







share|improve this answer












share|improve this answer



share|improve this answer










answered yesterday









zyy

638613




638613








  • 3




    Why should you use XeLaTeX for this?
    – TeXnician
    yesterday














  • 3




    Why should you use XeLaTeX for this?
    – TeXnician
    yesterday








3




3




Why should you use XeLaTeX for this?
– TeXnician
yesterday




Why should you use XeLaTeX for this?
– TeXnician
yesterday










up vote
0
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!)






share|improve this answer








New contributor




PGSan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.














  • 2




    Welcome! For the first paragraph look here.
    – manooooh
    yesterday

















up vote
0
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!)






share|improve this answer








New contributor




PGSan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.














  • 2




    Welcome! For the first paragraph look here.
    – manooooh
    yesterday















up vote
0
down vote










up vote
0
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!)






share|improve this answer








New contributor




PGSan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









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!)







share|improve this answer








New contributor




PGSan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this answer



share|improve this answer






New contributor




PGSan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









answered yesterday









PGSan

93




93




New contributor




PGSan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





PGSan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






PGSan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 2




    Welcome! For the first paragraph look here.
    – manooooh
    yesterday
















  • 2




    Welcome! For the first paragraph look here.
    – manooooh
    yesterday










2




2




Welcome! For the first paragraph look here.
– manooooh
yesterday






Welcome! For the first paragraph look here.
– manooooh
yesterday












heral is a new contributor. Be nice, and check out our Code of Conduct.










 

draft saved


draft discarded


















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.















 


draft saved


draft discarded














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





















































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







Popular posts from this blog

サソリ

広島県道265号伴広島線

Accessing regular linux commands in Huawei's Dopra Linux