Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.4905); Tue, 6 Aug 2002 21:48:07 +0200 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id g76Jl4VP024741 for ; Tue, 6 Aug 2002 21:47:08 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id g76Ja02T016665; Tue, 6 Aug 2002 21:36:00 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C23D82.2F653580" Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id g75M04Gr004568; Tue, 6 Aug 2002 21:35:50 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 5214 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 6 Aug 2002 21:35:50 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id g76JZogS011946 for ; Tue, 6 Aug 2002 21:35:50 +0200 Received: from mail14c.sanjose14-verio.com (mail14c.sanjose14-verio.com [128.121.143.6]) by relay.uni-heidelberg.de (8.12.4/8.12.4) with SMTP id g76JZeU5000094 for ; Tue, 6 Aug 2002 21:35:41 +0200 (MET DST) Received: from www.w3k.org (128.121.78.228) by mail14c.sanjose14-verio.com (RS ver 1.0.63s) with SMTP id 033921; Tue, 6 Aug 2002 15:35:24 -0400 (EDT) In-Reply-To: <200208061344.g76DiBj11924@sloth.e.kth.se> References: Return-Path: X-Mailer: QUALCOMM Windows Eudora Version 5.1 X-OriginalArrivalTime: 06 Aug 2002 19:48:07.0961 (UTC) FILETIME=[2FF7D890:01C23D82] X-Sender: wkorg0@w3k.org X-Scanned-By: MIMEDefang 2.6 (www dot roaringpenguin dot com slash mimedefang) x-loop-detect: 1 Content-class: urn:content-classes:message Subject: Re: LaTeX Error: which file? Date: Tue, 6 Aug 2002 20:35:24 +0100 Message-ID: A<5.1.0.14.0.20020806111131.04d8ddc8@w3k.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: LaTeX Error: which file? Thread-Index: AcI9gjAQ8uOY6Fn6S4SH0KnU43H8Sw== From: "Julius Smith" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4351 This is a multi-part message in MIME format. ------_=_NextPart_001_01C23D82.2F653580 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 03:44 PM 8/6/2002 +0200, Magnus Erixon wrote: >If you check the log-file you get more information! >It should be quite easy to find out where things got wrong. Thanks for the tip. What exactly should I search for in the log-file? = I cannot find any helpful additional information. Below is how the end of my log-file looks in this particular example. = After producing 325 pages, LaTeX complains about an error on "input line 21". After a time-consuming binary search, commenting out half of my \input lines at the top level each iteration, I determined that the indicated "line 21" was in a file processed just after page [26] was emitted. = There is no indication I can find anywhere in the log file that points back to that file as a possible source of trouble. (There could have been a warning about an unclosed \begin{itemize} when the offending file was processed after page [26], but there wasn't. In fact, the only = occurrence the word "itemize" in the log was after page [325] in the output, with = no indication of relevant source file.) In any case, I believe my original suggestion remains a needed improvement. To summarize that, after "input line 21", LaTeX should = have printed "in file matlab1.tex". Furthermore, "l.100" in the log-file = (see below), the line at which the error was detected, should have been = printed as "filters.tex: line 100:", or equivalent. I would be happy to supply the full log file, or even the entire = directory if anyone is interested. However, surely others have had this problem = on occasion. It can really be a time sink. Thanks for your consideration, Julius Smith CCRMA, Stanford ... [325]) ! LaTeX Error: \begin{itemize} on input line 21 ended by \end{document}. See the LaTeX manual or LaTeX Companion for explanation. Type H for immediate help. ... l.100 \end{document} ? x Here is how much of TeX's memory you used: 2916 strings out of 20887 31880 string characters out of 196273 92053 words of memory out of 350001 5621 multiletter control sequences out of 10000+15000 19851 words of font info for 76 fonts, out of 400000 for 1000 21 hyphenation exceptions out of 10000 32i,15n,31p,564b,777s stack positions out of = 3000i,100n,1500p,50000b,4000s Output written on filters.dvi (349 pages, 958056 bytes). > When LaTeX encounters an error, we see something like the following: > > ! LaTeX Error: \begin{itemize} on input line 21 ended by = \end{document}. > > However, I typically have many "\input" statements, so it is often = annoying > to figure out which file contains the offending line. (In an emacs = shell, > I routinely type "\C-u\C-r([a-z]" to get back to the last opened = file, but > this is only right some of the time.) It seems it should not be hard = to > improve the error message to say instead > > ! LaTeX Error: \begin{itemize} on input line 21 in foo.tex ended by > \end{document}. > > As an optimization, if only one user file has been seen, "in foo.tex" = could > be suppressed. > > Thanks for your consideration, > Julius ------_=_NextPart_001_01C23D82.2F653580 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: LaTeX Error: which file?

At 03:44 PM 8/6/2002 +0200, Magnus Erixon = wrote:
>If you check the log-file you get more = information!
>It should be quite easy to find out where things = got wrong.

Thanks for the tip.  What exactly should I search = for in the log-file?  I
cannot find any helpful additional = information.

Below is how the end of my log-file looks in this = particular example. After
producing 325 pages, LaTeX complains about an error = on "input line 21".
After a time-consuming binary search, commenting out = half of my \input
lines at the top level each iteration, I determined = that the indicated
"line 21" was in a file processed just = after page [26] was emitted.  There
is no indication I can find anywhere in the log file = that points back to
that file as a possible source of trouble.  = (There could have been a
warning about an unclosed \begin{itemize} when the = offending file was
processed after page [26], but there wasn't.  In = fact, the only occurrence
the word "itemize" in the log was after = page [325] in the output, with no
indication of relevant source file.)

In any case, I believe my original suggestion remains = a needed
improvement.  To summarize that, after = "input line 21", LaTeX should have
printed "in file matlab1.tex".  = Furthermore, "l.100" in the log-file (see
below), the line at which the error was detected, = should have been printed
as "filters.tex: line 100:", or = equivalent.

I would be happy to supply the full log file, or even = the entire directory
if anyone is interested.  However, surely others = have had this problem on
occasion.  It can really be a time sink.

Thanks for your consideration,
Julius Smith
CCRMA, Stanford

...
[325])

! LaTeX Error: \begin{itemize} on input line 21 ended = by \end{document}.

See the LaTeX manual or LaTeX Companion for = explanation.
Type  H <return>  for immediate = help.
  ...

l.100 \end{document}

? x

Here is how much of TeX's memory you used:
  2916 strings out of 20887
  31880 string characters out of 196273
  92053 words of memory out of 350001
  5621 multiletter control sequences out of = 10000+15000
  19851 words of font info for 76 fonts, out of = 400000 for 1000
  21 hyphenation exceptions out of 10000
  32i,15n,31p,564b,777s stack positions out of = 3000i,100n,1500p,50000b,4000s
Output written on filters.dvi (349 pages, 958056 = bytes).


 > When LaTeX encounters an error, we see = something like the following:
 >
 > ! LaTeX Error: \begin{itemize} on input = line 21 ended by \end{document}.
 >
 > However, I typically have many = "\input" statements, so it is often annoying
 > to figure out which file contains the = offending line. (In an emacs shell,
 > I routinely type = "\C-u\C-r([a-z]" to get back to the last opened file, = but
 > this is only right some of the time.) It = seems it should not be hard to
 > improve the error message to say = instead
 >
 > ! LaTeX Error: \begin{itemize} on input = line 21 in foo.tex ended by
 > \end{document}.
 >
 > As an optimization, if only one user file = has been seen, "in foo.tex" could
 > be suppressed.
 >
 > Thanks for your consideration,
 > Julius

------_=_NextPart_001_01C23D82.2F653580--