In plain TeX, \bye marks the end of the TeX document. Yet why is such a command even needed? TeX should be quite able to see for itself that here, the file stops, and there is nothing more to find. I do not see why it needs a command to tell it so.

I realise that LaTeX also has such a command, \end{document}; but that one seems natural because it creates symmetry with \begin{document}.

  • 4
    You don't need a file, you can input all the stuff using STDIN. At the end of a compile information is written to the auxiliary files and they are properly saved. \end{document} is the LaTeX equivalent. – Johannes_B Jun 7 '15 at 20:09
  • 9
    I think originally DEK just typed away at the TeX prompt, and then typed \bye when he was done... :-) The primitive command that ends the input is \end, and clearly it's helpful to be able to end a complex file at various points depending on what you are doing. – Thruston Jun 7 '15 at 20:10

The reason is in the definition:


So \bye doesn't just issue \end (that would by itself issue \par, but not \vfill): it also performs \supereject, which is


Why a -20000 penalty? The reason is in the output routine:

  \ifnum\outputpenalty>-\@MM \else\dosupereject\fi}

If the penalty that triggers the output routine is greater than -20000, nothing special is done after advancing the page number. Otherwise \dosupereject comes into action:

\def\dosupereject{\ifnum\insertpenalties>\z@ % something is being held over

The macro ensures all pending insertions are shipped out, by repeated call of \supereject until \insertpenalties is not positive any more.

One can call \supereject at any time (which is the reason for \par at the beginning), for instance when a chapter is beginning.

Some more ideas from comments to the question and to the answer

TeX can be run interactively and it goes interactive if the main input file ends without an \end command (or makes an “Emergency stop” if the running mode is not interactive). Due to this possible interactivity, an implied \end command would be undesirable.

Only a few operating systems add an implied <EOF> marker at the end of a file, which could be ^^D (EOT) or ^^Z. The ^^Z character used to be added in MS-DOS files, but not all text editors were compliant.

Depending on the operating system and the shell, hitting Control-D at the interactive prompt can stop the execution, but no \end command is executed.

Since TeX keeps a stack of the \input files, it knows when it has reached the end of the main file, so a possible feature could be “insert the token \end when you reach the end of the main file”. However, there should also be a “disable automatic \end” feature to allow interaction at the end of the file. There is a similar feature in TeX: when switching from horizontal to vertical mode due to finding a <vertical command>, TeX adds a \par token (which could not be the primitive \par any more). However, the situation for an “automatic \end” is very different: breaking a paragraph into files is a common TeX activity, while the end of the main file just happen once.

Having the terminating \end allows for adding structure to it. One could redefine \end (after keeping a copy of the primitive) to do other bookkeeping business like \bye does. So


could be thought of, but it was not Knuth's choice (and it wouldn't be mine as well).

Finally, having \end (or \bye or \end{document}) at the end of the main file allows for putting comments and additional material after the end marker, which wouldn't be possible otherwise. Since most programming languages require programs to be explicitly terminated, I don't see why TeX should be an exception.

  • 4
    And here I thought \bye was a primitive. ;-) – Gaussler Jun 7 '15 at 20:21
  • 1
    I'm surprised the plain TeX output routine is such a short piece of code. OR is supposed to be one of the most difficult aspects of TeX. – Gaussler Jun 7 '15 at 20:46
  • 5
    @Gaussler You should look at \makeheadline, \pagebody and \makefootline. ;-) – egreg Jun 7 '15 at 20:48
  • 2
    It's not TeX Live that does something special when Ctrl-D is pressed, but the terminal driver in Unix which (in the default "cooked" mode) converts the Ctrl-D into an ordinary end-of-file event before the TeX process even sees it. TeX will then make the same kind of emergency stop as when an actual input file ends. (Note, for example, that typing ^^D at the * prompt -- that is, hat-hat-D -- does not do this). – Henning Makholm Jun 8 '15 at 13:52
  • 2
    @Gaussler \mathchardef\@MM=20000 (M stands for myriad). Note that a penalty of –2000 wouldn't force a page break. – egreg Jun 8 '15 at 19:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.