Emergency stop in plain TeX, pdfTeX, XeTeX and LuaTeX?Problem viewing document in TEXmaker “Fontspec requires XeTeX or LuaTeX”fmtversion not the same with xelatex and pdflatexHow do I use psvectorian with xelatexXeLaTeX does not load newtxmath with LinuxLibertine (sometimes)Cannot make correct line breakfrench: Add usepackagefontspec to the preamble of your documentUsing Xetex to Include bmp file into document using Plain TeXHu and Ho do not appear in the lualatex output PDFamscls and ams fonts with TexLive, installing fontsXetex stopped working after update to Mojave

In "Avengers: Endgame", what does this name refer to?

Python 3 - simple temperature program version 1.3

Dimmer switch not connected to ground

What does のそ mean on this picture?

How do I, as a DM, handle a party that decides to set up an ambush in a dungeon?

What is monoid homomorphism exactly?

Sci-fi/fantasy book - ships on steel runners skating across ice sheets

Is there any other simpler way to draw the following cross section?

Why increasing of the temperature of the objects like wood, paper etc. doesn't fire them?

What would happen if I combined this polymer and this metal (assuming I can)

How to deal with employer who keeps me at work after working hours

Make me a minimum magic sum

Can I combine SELECT TOP() with the IN operator?

Class Not Passing SObject By Reference

Reverse ColorFunction or ColorData

What is a precise issue with allowing getters?

Which version of the Squat Nimbleness feat is correct?

Two denim hijabs

What is a common way to tell if an academic is "above average," or outstanding in their field? Is their h-index (Hirsh index) one of them?

HSA - Continue to Invest?

What does the copyright in a dissertation protect exactly?

Is it normal for gliders not to have attitude indicators?

Can an earth elemental drag a tiny creature underground with Earth Glide?

Can an Iranian citizen enter the USA on a Dutch passport?



Emergency stop in plain TeX, pdfTeX, XeTeX and LuaTeX?


Problem viewing document in TEXmaker “Fontspec requires XeTeX or LuaTeX”fmtversion not the same with xelatex and pdflatexHow do I use psvectorian with xelatexXeLaTeX does not load newtxmath with LinuxLibertine (sometimes)Cannot make correct line breakfrench: Add usepackagefontspec to the preamble of your documentUsing Xetex to Include bmp file into document using Plain TeXHu and Ho do not appear in the lualatex output PDFamscls and ams fonts with TexLive, installing fontsXetex stopped working after update to Mojave













1















I'm using <TeX_Engine> -jobname=TEX_TESTING -halt-on-error -interaction=nonstopmode <my_code> to TeX the one-line code Abye. It does not work. Here are the logs:



Plain TeX:



This is TeX, Version 3.14159265 (TeX Live 2017) (preloaded format=tex
2017.5.23) 5 MAY 2019 17:59
**Abye

! Emergency stop. <to be read again>
par bye ->par
vfill supereject end <*> Abye
No pages of output.


pdfTeX:



This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017) (preloaded format=pdftex 2017.5.23) 5 MAY 2019 17:59
entering extended mode
restricted write18 enabled.
%&-line parsing enabled.
**Abye

! Emergency stop.
<to be read again>
par
bye ->par
vfill supereject end
<*> Abye

! ==> Fatal error occurred, no output PDF file produced!


XeTeX:



This is XeTeX, Version 3.14159265-2.6-0.99998 (TeX Live 2017) (preloaded format=xetex 2017.5.23) 5 MAY 2019 17:59
entering extended mode
restricted write18 enabled.
%&-line parsing enabled.
**Abye

! Emergency stop.
<to be read again>
par
bye ->par
vfill supereject end
<*> Abye

No pages of output.


LuaTeX:



This is LuaTeX, Version 1.0.4 (TeX Live 2017) (format=luatex 2017.5.23) 5 MAY 2019 17:59
restricted system commands enabled.
**Abye

! Emergency stop.
<to be read again>
par
bye ->par
vfill supereject end
<*> Abye

! ==> Fatal error occurred, no output PDF file produced!


What happened? In TeXShop things work. Is it because of -halt-on-error or -interaction=nonstopmode? I can't get rid of either because I really do not want stopping to happen under any circumstances.



What I need is the simplest valid TeX/XeTeX/LuaTeX code containing a certain string (here it is A). That's it.










share|improve this question






















  • The ** prompt expects a file name, so you have to type relax Abye.

    – Henri Menke
    56 mins ago
















1















I'm using <TeX_Engine> -jobname=TEX_TESTING -halt-on-error -interaction=nonstopmode <my_code> to TeX the one-line code Abye. It does not work. Here are the logs:



Plain TeX:



This is TeX, Version 3.14159265 (TeX Live 2017) (preloaded format=tex
2017.5.23) 5 MAY 2019 17:59
**Abye

! Emergency stop. <to be read again>
par bye ->par
vfill supereject end <*> Abye
No pages of output.


pdfTeX:



This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017) (preloaded format=pdftex 2017.5.23) 5 MAY 2019 17:59
entering extended mode
restricted write18 enabled.
%&-line parsing enabled.
**Abye

! Emergency stop.
<to be read again>
par
bye ->par
vfill supereject end
<*> Abye

! ==> Fatal error occurred, no output PDF file produced!


XeTeX:



This is XeTeX, Version 3.14159265-2.6-0.99998 (TeX Live 2017) (preloaded format=xetex 2017.5.23) 5 MAY 2019 17:59
entering extended mode
restricted write18 enabled.
%&-line parsing enabled.
**Abye

! Emergency stop.
<to be read again>
par
bye ->par
vfill supereject end
<*> Abye

No pages of output.


LuaTeX:



This is LuaTeX, Version 1.0.4 (TeX Live 2017) (format=luatex 2017.5.23) 5 MAY 2019 17:59
restricted system commands enabled.
**Abye

! Emergency stop.
<to be read again>
par
bye ->par
vfill supereject end
<*> Abye

! ==> Fatal error occurred, no output PDF file produced!


What happened? In TeXShop things work. Is it because of -halt-on-error or -interaction=nonstopmode? I can't get rid of either because I really do not want stopping to happen under any circumstances.



What I need is the simplest valid TeX/XeTeX/LuaTeX code containing a certain string (here it is A). That's it.










share|improve this question






















  • The ** prompt expects a file name, so you have to type relax Abye.

    – Henri Menke
    56 mins ago














1












1








1








I'm using <TeX_Engine> -jobname=TEX_TESTING -halt-on-error -interaction=nonstopmode <my_code> to TeX the one-line code Abye. It does not work. Here are the logs:



Plain TeX:



This is TeX, Version 3.14159265 (TeX Live 2017) (preloaded format=tex
2017.5.23) 5 MAY 2019 17:59
**Abye

! Emergency stop. <to be read again>
par bye ->par
vfill supereject end <*> Abye
No pages of output.


pdfTeX:



This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017) (preloaded format=pdftex 2017.5.23) 5 MAY 2019 17:59
entering extended mode
restricted write18 enabled.
%&-line parsing enabled.
**Abye

! Emergency stop.
<to be read again>
par
bye ->par
vfill supereject end
<*> Abye

! ==> Fatal error occurred, no output PDF file produced!


XeTeX:



This is XeTeX, Version 3.14159265-2.6-0.99998 (TeX Live 2017) (preloaded format=xetex 2017.5.23) 5 MAY 2019 17:59
entering extended mode
restricted write18 enabled.
%&-line parsing enabled.
**Abye

! Emergency stop.
<to be read again>
par
bye ->par
vfill supereject end
<*> Abye

No pages of output.


LuaTeX:



This is LuaTeX, Version 1.0.4 (TeX Live 2017) (format=luatex 2017.5.23) 5 MAY 2019 17:59
restricted system commands enabled.
**Abye

! Emergency stop.
<to be read again>
par
bye ->par
vfill supereject end
<*> Abye

! ==> Fatal error occurred, no output PDF file produced!


What happened? In TeXShop things work. Is it because of -halt-on-error or -interaction=nonstopmode? I can't get rid of either because I really do not want stopping to happen under any circumstances.



What I need is the simplest valid TeX/XeTeX/LuaTeX code containing a certain string (here it is A). That's it.










share|improve this question














I'm using <TeX_Engine> -jobname=TEX_TESTING -halt-on-error -interaction=nonstopmode <my_code> to TeX the one-line code Abye. It does not work. Here are the logs:



Plain TeX:



This is TeX, Version 3.14159265 (TeX Live 2017) (preloaded format=tex
2017.5.23) 5 MAY 2019 17:59
**Abye

! Emergency stop. <to be read again>
par bye ->par
vfill supereject end <*> Abye
No pages of output.


pdfTeX:



This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017) (preloaded format=pdftex 2017.5.23) 5 MAY 2019 17:59
entering extended mode
restricted write18 enabled.
%&-line parsing enabled.
**Abye

! Emergency stop.
<to be read again>
par
bye ->par
vfill supereject end
<*> Abye

! ==> Fatal error occurred, no output PDF file produced!


XeTeX:



This is XeTeX, Version 3.14159265-2.6-0.99998 (TeX Live 2017) (preloaded format=xetex 2017.5.23) 5 MAY 2019 17:59
entering extended mode
restricted write18 enabled.
%&-line parsing enabled.
**Abye

! Emergency stop.
<to be read again>
par
bye ->par
vfill supereject end
<*> Abye

No pages of output.


LuaTeX:



This is LuaTeX, Version 1.0.4 (TeX Live 2017) (format=luatex 2017.5.23) 5 MAY 2019 17:59
restricted system commands enabled.
**Abye

! Emergency stop.
<to be read again>
par
bye ->par
vfill supereject end
<*> Abye

! ==> Fatal error occurred, no output PDF file produced!


What happened? In TeXShop things work. Is it because of -halt-on-error or -interaction=nonstopmode? I can't get rid of either because I really do not want stopping to happen under any circumstances.



What I need is the simplest valid TeX/XeTeX/LuaTeX code containing a certain string (here it is A). That's it.







xetex pdftex luatex plain-tex






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 1 hour ago









Ying ZhouYing Zhou

1209




1209












  • The ** prompt expects a file name, so you have to type relax Abye.

    – Henri Menke
    56 mins ago


















  • The ** prompt expects a file name, so you have to type relax Abye.

    – Henri Menke
    56 mins ago

















The ** prompt expects a file name, so you have to type relax Abye.

– Henri Menke
56 mins ago






The ** prompt expects a file name, so you have to type relax Abye.

– Henri Menke
56 mins ago











1 Answer
1






active

oldest

votes


















3














From the TeXbook page 23




The ‘**’ is TEX’s way of asking you for an input file name.




Since you want to use TeX interactively rather than processing a file, you have to let TeX know by saying relax. The error you see comes from the fact that TeX tries to read Abye as a file name, which involves full expansion of bye which is defined as



outerdefbyeparvfillsuperejectend


which immediately chokes on par because that is obviously not a legal part of a file name.



So if instead Abye you say relax Abye it works as expected:



This is TeX, Version 3.14159265 (TeX Live 2019) (preloaded format=tex)
**relax Abye
[1]
Output written on texput.dvi (1 page, 208 bytes).
Transcript written on texput.log.


You can also type only relax at the ** prompt and then supply your commands at the * prompt.



This is TeX, Version 3.14159265 (TeX Live 2019) (preloaded format=tex)
**relax

*Abye
[1]
Output written on texput.dvi (1 page, 208 bytes).
Transcript written on texput.log.





share|improve this answer




















  • 1





    Great! That does work! I mean 'relax Abye'.

    – Ying Zhou
    50 mins ago












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',
autoActivateHeartbeat: false,
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
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f489359%2femergency-stop-in-plain-tex-pdftex-xetex-and-luatex%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









3














From the TeXbook page 23




The ‘**’ is TEX’s way of asking you for an input file name.




Since you want to use TeX interactively rather than processing a file, you have to let TeX know by saying relax. The error you see comes from the fact that TeX tries to read Abye as a file name, which involves full expansion of bye which is defined as



outerdefbyeparvfillsuperejectend


which immediately chokes on par because that is obviously not a legal part of a file name.



So if instead Abye you say relax Abye it works as expected:



This is TeX, Version 3.14159265 (TeX Live 2019) (preloaded format=tex)
**relax Abye
[1]
Output written on texput.dvi (1 page, 208 bytes).
Transcript written on texput.log.


You can also type only relax at the ** prompt and then supply your commands at the * prompt.



This is TeX, Version 3.14159265 (TeX Live 2019) (preloaded format=tex)
**relax

*Abye
[1]
Output written on texput.dvi (1 page, 208 bytes).
Transcript written on texput.log.





share|improve this answer




















  • 1





    Great! That does work! I mean 'relax Abye'.

    – Ying Zhou
    50 mins ago
















3














From the TeXbook page 23




The ‘**’ is TEX’s way of asking you for an input file name.




Since you want to use TeX interactively rather than processing a file, you have to let TeX know by saying relax. The error you see comes from the fact that TeX tries to read Abye as a file name, which involves full expansion of bye which is defined as



outerdefbyeparvfillsuperejectend


which immediately chokes on par because that is obviously not a legal part of a file name.



So if instead Abye you say relax Abye it works as expected:



This is TeX, Version 3.14159265 (TeX Live 2019) (preloaded format=tex)
**relax Abye
[1]
Output written on texput.dvi (1 page, 208 bytes).
Transcript written on texput.log.


You can also type only relax at the ** prompt and then supply your commands at the * prompt.



This is TeX, Version 3.14159265 (TeX Live 2019) (preloaded format=tex)
**relax

*Abye
[1]
Output written on texput.dvi (1 page, 208 bytes).
Transcript written on texput.log.





share|improve this answer




















  • 1





    Great! That does work! I mean 'relax Abye'.

    – Ying Zhou
    50 mins ago














3












3








3







From the TeXbook page 23




The ‘**’ is TEX’s way of asking you for an input file name.




Since you want to use TeX interactively rather than processing a file, you have to let TeX know by saying relax. The error you see comes from the fact that TeX tries to read Abye as a file name, which involves full expansion of bye which is defined as



outerdefbyeparvfillsuperejectend


which immediately chokes on par because that is obviously not a legal part of a file name.



So if instead Abye you say relax Abye it works as expected:



This is TeX, Version 3.14159265 (TeX Live 2019) (preloaded format=tex)
**relax Abye
[1]
Output written on texput.dvi (1 page, 208 bytes).
Transcript written on texput.log.


You can also type only relax at the ** prompt and then supply your commands at the * prompt.



This is TeX, Version 3.14159265 (TeX Live 2019) (preloaded format=tex)
**relax

*Abye
[1]
Output written on texput.dvi (1 page, 208 bytes).
Transcript written on texput.log.





share|improve this answer















From the TeXbook page 23




The ‘**’ is TEX’s way of asking you for an input file name.




Since you want to use TeX interactively rather than processing a file, you have to let TeX know by saying relax. The error you see comes from the fact that TeX tries to read Abye as a file name, which involves full expansion of bye which is defined as



outerdefbyeparvfillsuperejectend


which immediately chokes on par because that is obviously not a legal part of a file name.



So if instead Abye you say relax Abye it works as expected:



This is TeX, Version 3.14159265 (TeX Live 2019) (preloaded format=tex)
**relax Abye
[1]
Output written on texput.dvi (1 page, 208 bytes).
Transcript written on texput.log.


You can also type only relax at the ** prompt and then supply your commands at the * prompt.



This is TeX, Version 3.14159265 (TeX Live 2019) (preloaded format=tex)
**relax

*Abye
[1]
Output written on texput.dvi (1 page, 208 bytes).
Transcript written on texput.log.






share|improve this answer














share|improve this answer



share|improve this answer








edited 49 mins ago

























answered 52 mins ago









Henri MenkeHenri Menke

78.7k9172285




78.7k9172285







  • 1





    Great! That does work! I mean 'relax Abye'.

    – Ying Zhou
    50 mins ago













  • 1





    Great! That does work! I mean 'relax Abye'.

    – Ying Zhou
    50 mins ago








1




1





Great! That does work! I mean 'relax Abye'.

– Ying Zhou
50 mins ago






Great! That does work! I mean 'relax Abye'.

– Ying Zhou
50 mins ago


















draft saved

draft discarded
















































Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f489359%2femergency-stop-in-plain-tex-pdftex-xetex-and-luatex%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

Siegen Nawigatsjuun

Log på Navigationsmenu

Log på Navigationsmenu