diff options
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typend.html')
-rw-r--r-- | Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typend.html | 43 |
1 files changed, 43 insertions, 0 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typend.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typend.html new file mode 100644 index 00000000000..76ef208ec98 --- /dev/null +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typend.html @@ -0,0 +1,43 @@ +<head> +<title>UK TeX FAQ -- question label typend</title> +</head><body> +<h3>“Please type a command or say <code>\</code><code>end</code>”</h3> +<p/>Sometimes, when you are running (La)TeX, it will abruptly stop and +present you with a prompt (by default, just a <code>*</code> character). Many +people (including this author) will reflexively hit the ‘return’ +key, pretty much immediately, and of course this is no help at all — +TeX just says: +<pre> +(Please type a command or say `\end') +</pre> +and prompts you again. +<p/>What’s happened is that your (La)TeX file has finished prematurely, +and TeX has fallen back to a supposed including file, from the +terminal. This could have happened simply because you’ve omitted +the <code>\</code><code>bye</code> (Plain TeX), <code>\</code><code>end{document}</code> (LaTeX), or +whatever. Other common errors are failure to close the braces round a +command’s argument, or (in LaTeX) failure to close a verbatim +environment: in such cases you’ve already read and accepted an +error message about encountering end of file while scanning something. +<p/>If the error is indeed because you’ve forgotten to end your document, +you can insert the missing text: if you’re running Plain TeX, the +advice, to “say <code>\</code><code>end</code>” is good enough: it will kill the run; if +you’re running LaTeX, the argument will be necessary: +<code>\</code><code>end{document}</code>. +<p/>However, as often as not this isn’t the problem, and (short of +debugging the source of the document before ending) brute force is +probably necessary. Excessive force (killing the job that’s +running TeX) is to be avoided: there may well be evidence in the +<code>.log</code> file that will be useful in determining what the +problem is — so the aim is to persuade TeX to shut itself down +and hence flush all log output to file. +<p/>If you can persuade TeX to read it, an end-of-file indication +(control-<code>D</code> under Unix, control-<code>Z</code> under Windows) will provoke +TeX to report an error and exit immediately. Otherwise you should +attempt to provoke an error dialogue, from which you can exit (using +the <code>x</code> ‘command’). An accessible error could well be inserting an +illegal character: what it is will depend on what macros you are +running. If you can’t make that work, try a silly command name or +two. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typend">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typend</a> +</body> |