[texworks] Auto Compiling

Joseph Wright joseph.wright at morningstar2.co.uk
Wed Jan 22 08:00:45 CET 2014


On 21/01/2014 22:31, Reinhard Kotucha wrote:
> On 2014-01-21 at 21:11:55 +0000, Philip Taylor wrote:
>
>   > Joseph Wright wrote:
>   >
>   > > TeX can be instructed to run past most
>   > > errors by giving the command-line option
>   > >
>   > >   -interaction=nonstopmode
>   >
>   > So what happens in the second scenario below, Joseph ?
>   > In the first, all is fine and as expected; in the second,
>   > an "Emergency stop" is generated when \relax is entered.
>   >
>   > Philip Taylor
>   > --------
>   > C:\Path>tex
>   > This is TeX, Version 3.1415926 (TeX Live 2013/W32TeX)
>   > **\relax
>   >
>   > *\end
>   > No pages of output.
>   > Transcript written on texput.log.
>   >
>   > C:\Path>tex -interaction=nonstopmode
>   > This is TeX, Version 3.1415926 (TeX Live 2013/W32TeX)
>   > **\relax
>   > ! Emergency stop.
>   > <*> \relax
>   >
>   > No pages of output.
>   > Transcript written on texput.log.
>   >
>   > C:\Windows\system32>
>
> Isn't the behavior in the second scenario exactly what is required?
> Here the program finishes without user interaction and returns
> exit code 1.  This is what I expect when it's running within an IDE.
>
> Regards,
>    Reinhard

Non-stop mode is meant for processing files, not input at the terminal! 
On my system (TL2013, Mac), I see

palladium:siunitx joseph$ pdftex -interaction=nonstopmode

This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013)
  restricted \write18 enabled.
**Please type the name of your input file.
**

for which \relax is an emergency stop: no file name. That's entirely 
consistent with what nonstopmode is for.
--
Joseph Wright


More information about the texworks mailing list