Thread: [MiKTeX] No Error message end{document}
MiKTeX source code moved to GitHub
Brought to you by:
csc
From: Lukas T. <nju...@ya...> - 2006-09-26 13:15:14
|
I use WinShell to edit LaTeX files. Recently I forgot to put a \end{documen= t} at the end of my file. With MiKTeX 2.4 this would have created a error m= essage, but with 2.5 there is no error. Even a DVI-File was produced - Howe= ver, it was corrupt.=0A=0AWhen I run latex from the console, the compiler s= tops after parsing the file and I can wirte \end{document} directly in the = console which at the end creates a valid DVI file.=0A=0AMy question is: Is = it normal, that forgetting \end{document} doesn't create a error or is this= a bug of MiKTeX 2.5?=0A=0AGreez=0A=0ALukas=0A=0A=0A=0A=0A=09=09=0A________= ___________________________________________________ =0ATelefonate ohne weit= ere Kosten vom PC zum PC: http://messenger.yahoo.de |
From: Paul T. <pa...@wu...> - 2006-09-26 13:45:16
|
At 08:14 AM 9/26/2006, you wrote: >I use WinShell to edit LaTeX files. Recently I forgot to put a >\end{document} at the end of my file. With MiKTeX 2.4 this would have >created a error message, but with 2.5 there is no error. Even a DVI-File >was produced - However, it was corrupt. > >When I run latex from the console, the compiler stops after parsing the >file and I can wirte \end{document} directly in the console which at the >end creates a valid DVI file. > >My question is: Is it normal, that forgetting \end{document} doesn't >create a error or is this a bug of MiKTeX 2.5? > >Greez > >Lukas I suggest adding \end{document} to your documents. > >___________________________________________________________ >Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de > >------------------------------------------------------------------------- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share your >opinions on IT & business topics through brief surveys -- and earn cash >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >_______________________________________________ >MiKTeX-Users mailing list >MiK...@li... >https://lists.sourceforge.net/lists/listinfo/miktex-users Paul A. Thompson, Ph.D. Division of Biostatistics Washington University School of Medicine 660 S. Euclid, St. Louis, MO 63110 314-747-3793 pa...@wu... |
From: Cornelius C. N. <no...@it...> - 2006-09-27 13:19:50
|
On Tue, 26 Sep 2006, Paul Thompson wrote: > At 08:14 AM 9/26/2006, you wrote: >> I use WinShell to edit LaTeX files. Recently I forgot to put a >> \end{document} at the end of my file. With MiKTeX 2.4 this would have >> created a error message, but with 2.5 there is no error. Even a DVI-File >> was produced - However, it was corrupt. >> >> When I run latex from the console, the compiler stops after parsing the >> file and I can wirte \end{document} directly in the console which at the >> end creates a valid DVI file. >> >> My question is: Is it normal, that forgetting \end{document} doesn't >> create a error or is this a bug of MiKTeX 2.5? >> >> Greez >> >> Lukas > > I suggest adding \end{document} to your documents. > Excellent suggestion!! But if you really still want to know why: (i) this is obviously a LaTeX, not a MikTeX question -- (ii) so therefore, to find out what's going on, you should check if MiKTeX 2.4 and MiKTeX 2.5 invoke different versions of LaTeX (which I doubt), and if so, check if the feature is due to that version difference (which I doubt to the point of saying that's impossible). (iii) if your curious feature appears in WinShell, WITH THE SAME version of LaTeX, it could only be due to a different handling of your LaTeX source by 2 different versions of WinShell as used by MiKTeX 2.4 and MiKTeX 2.5; for example, I could imagine that a WinShell programmer would have the idea of supplying an \end{document} when reaching the physical end of the source file. IMHO, that would be pretty bad programming practice; but various people have various ideas ... So, to sum up: after you have satisfied your curiosity, follow the suggestion of the previous correspondent! ccn. -- ................................................................. Prof.Dr. Cornelius C. Noack Phones: Inst. f. Theor. Physik FB 1 office : +49 (421) 218-2427 Universit"at Bremen secretary: -2422 Otto-Hahn-Allee Fax : -4869 D - 28334 Bremen home : +49 (421) 34 22 36 Fax: 346 7872 E-mail: noack at itp.uni-bremen.de or ccnoack at mailaps.org WWW-page: www.itp.uni-bremen.de/~noack ................................................................. |
From: Alan R. <ri...@ec...> - 2006-09-27 14:29:21
|
Cornelius C. Noack wrote: > On Tue, 26 Sep 2006, Paul Thompson wrote: > >> At 08:14 AM 9/26/2006, you wrote: >>> I use WinShell to edit LaTeX files. Recently I forgot to put a >>> \end{document} at the end of my file. With MiKTeX 2.4 this would have >>> created a error message, but with 2.5 there is no error. Even a DVI-File >>> was produced - However, it was corrupt. >>> >>> When I run latex from the console, the compiler stops after parsing the >>> file and I can wirte \end{document} directly in the console which at the >>> end creates a valid DVI file. >>> >>> My question is: Is it normal, that forgetting \end{document} doesn't >>> create a error or is this a bug of MiKTeX 2.5? >>> >>> Greez >>> >>> Lukas >> I suggest adding \end{document} to your documents. >> > Excellent suggestion!! But if you really still want to know why: > (i) this is obviously a LaTeX, not a MikTeX question -- I seem to remember MiKTeX 2.4 specifically flagging a missing \end{document} as an error, but the behavior I see in MiKTeX 2.5 -- which ends with an emergency stop and a corrupt DVI -- is consistent with what I observe in teTeX. I don't know if one is "more correct" than the other with respect to whatever standards and specifications govern these things. > (ii) so therefore, to find out what's going on, you should check > if MiKTeX 2.4 and MiKTeX 2.5 invoke different versions of > LaTeX (which I doubt), and if so, check if the feature is due > to that version difference (which I doubt to the point of > saying that's impossible). Strictly speaking, I suppose it's true that they don't invoke different versions of LaTeX. They do, however, invoke different programs when you run latex.exe. MiKTeX 2.4 invokes eTeX while MiKTeX 2.5 invokes pdfeTeX. The version of teTeX I used in my test above is an old one that uses a third program, plain old TeX. All of them accomplish LaTeX runs by using a LaTeX format file to force them to act like LaTeX, but as I understand it they are completely different programs. I suppose it's possible that eTeX produces a 'missing \end{document}' error while TeX and pdfeTeX produce emergency stops when \end{document} is not present, though I have no idea whether that explanation is correct. > (iii) if your curious feature appears in WinShell, WITH THE SAME > version of LaTeX, it could only be due to a different > handling of your LaTeX source by 2 different versions > of WinShell as used by MiKTeX 2.4 and MiKTeX 2.5; for > example, I could imagine that a WinShell programmer would > have the idea of supplying an \end{document} when reaching the > physical end of the source file. IMHO, that would be > pretty bad programming practice; but various people have > various ideas ... I'm not familiar with WinShell, but I seriously doubt it's supplying an \end{document} without the user's knowledge. More likely it's simply not detecting the emergency stop when it parses the log file. WinEdt 5.4 also misses the emergency stop, resulting in a run that seems successful but produces a corrupt DVI. If you open the log file and check it yourself it's quite easy to spot the emergency stop. Emacs/AUCTeX detects the emergency stop and alerts the user that there's a problem. > So, to sum up: after you have satisfied your curiosity, follow the > suggestion of the previous correspondent! I think the OP's point is that it would be easier to find and correct the error if the error were more apparent. While this appears to be an editor issue, with the change in MiKTeX's behavior it's hardly surprising that he would think it's a MiKTeX issue. Alan |