bug-auctex
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-AUCTeX] 2009-04-05; Switching to web2c 7.5.6 buffer instead of


From: Ralf Angeli
Subject: Re: [Bug-AUCTeX] 2009-04-05; Switching to web2c 7.5.6 buffer instead of source buffer
Date: Sun, 05 Jul 2009 14:34:09 +0200

Please keep the mailing list copied!

* Pierre Lorenzon (2009-07-05) writes:

> From: Ralf Angeli <address@hidden>
>
>> Probably.  But since you failed to include an example for reproducing
>> the problem I cannot say for certain.
>
>   Here is the beginning of the output. Anyway those buffers are so big
>   that I did not want to include it in the mail :
>
>   ---
>
> Running `LaTeX' on `Cahier' with ``latex  -interaction=nonstopmode "\input" 
> Cahier.tex''
> This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
[...]
> Package amsmath Warning: Foreign command \over;
> (amsmath)                \frac or \genfrac should be used instead
> (amsmath)                 on input line 341.
[...]
> LaTeX Warning: Command \` invalid in math mode on input line 390.
>
>
> Overfull \hbox (655.6115pt too wide) detected at line 400
> \OML/cmm/m/it/12 x[]:x[]  \OT1/cmr/m/n/12 =  \OML/cmm/m/it/12 
> x[]\OT1/cmr/m/n/12 (\OML/cmm/m/it/12 x[]x[] \OMS/cmsy/m/n/12 ^^@ 
> \OT1/cmr/m/n/12 2\OML/cmm/m/it/
> 12 x[]\OT1/cmr/m/n/12 )  =  (\OML/cmm/m/it/12 x[] \OT1/cmr/m/n/12 + 
> \OML/cmm/m/it/12 ix[]\OT1/cmr/m/n/12 )\OML/cmm/m/it/12 x[] \OMS/cmsy/m/n/12 
> ^^@ \OT1/cmr/m/n/12 2\OML/cmm/m/it/12 x[]:x[]  \OT1/cmr/m/n/12 =  
> \OML/cmm/m/it/12 x[]x[] \OT1/cmr/m/n/12 + (\OML/cmm/m/it/12 i 
> \OMS/cmsy/m/n/12 ^^@ \OT1/cmr/m/n/12 2)[\OML/cmm/m/it/12 x[] \OT1/cmr/m/n/12 
> + 2; +2\OML/cmm/m/it/12 ix[] \OT1/cmr/m/n/12 + 1; +(\OML/cmm/m/it/12 i[] 
> \OMS/cmsy/m/n/12 ^^@ \OML/cmm/m/it/12 i\OT1/cmr/m/n/12 )\OML/cmm/m/it/12 
> x[]\OT1/cmr/m/n/12 ]  =  \OML/cmm/m/it/12 x[] \OT1/cmr/m/n/12 + 3 + 
> 2(\OML/cmm/m/it/12 i \OT1/cmr/m/n/12 + 1)\OML/cmm/m/it/12 x[] \OT1/cmr/m/n/12 
> + 2; +(\OML/cmm/m/it/12 i[] \OT1/cmr/m/n/12 + 2\OML/cmm/m/it/12 i 
> \OT1/cmr/m/n/12 + 1 \OMS/cmsy/m/n/12 ^^@ \OML/cmm/m/it/12 i \OMS/cmsy/m/n/12 
> ^^@ \OT1/cmr/m/n/12 1)\OML/cmm/m/it/12 x[] \OT1/cmr/m/n/12 + 1; 
> +(\OML/cmm/m/it/12 i \OMS/cmsy/m/n/12 ^^@ \OT1/cmr/m/n/12 2)[\OML/cmm/m/it/12 
> x[] \OT1/cmr/m/n/12 + 2; +2\OML/cmm/m/it/12 ix[] \OT1/cmr/m/n/12 + 1; 
> +(\OML/cmm/m/it/12 i[] \OMS/cmsy/m/n/12 ^^@ \OML/cmm/m/it/12 i\OT1/cmr/m/n/12 
> )\OML/cmm/m/it/12 x[]\OT1/cmr/m/n/12 ]  =  \OML/cmm/m/it/12 x[] 
> \OT1/cmr/m/n/12 + 3; +3\OML/cmm/m/it/12 ix[] \OT1/cmr/m/n/12 + 2; 
> 3(\OML/cmm/m/it/12 i[] \OMS/cmsy/m/n/12 ^^@ \OML/cmm/m/it/12 i\OT1/cmr/m/n/12 
> )\OML/cmm/m/it/12 x[] \OT1/cmr/m/n/12 + 1; +\OML/cmm/m/it/12 i\OT1/cmr/m/n/12 
> (\OML/cmm/m/it/12 i \OMS/cmsy/m/n/12 ^^@ \OT1/cmr/m/n/12 1)(\OML/cmm/m/it/12 
> i \OMS/cmsy/m/n/12 ^^@ \OT1/cmr/m/n/12 2)
[...]
> [] \U/msb/m/n/12 Z\OT1/cmr/m/n/12 [[]] \OML/cmm/m/it/12 :
> [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44] [45] [46]) [47] [48]
> ! Missing \endgroup inserted.
> <inserted text> 
>                 \endgroup 
> l.158     \begin{eqnarray*}
>                            
> ! Extra alignment tab has been changed to \cr.
> <template> \egroup \endtemplate 
>                                 
> l.160       &\mbox{d'où}&
>                          \\
> ! Extra alignment tab has been changed to \cr.
> <template> \egroup \endtemplate 
>                                 
> ---
>
> I think, lines after this are not significant. Here is the
> first error.  Parser should go backward and find first pair of
> not closed parenthesis, shouldn't it ? I suspect it is the
> normal behavior of this engine. 

The parser is working with a stack where a new entry is pushed on the
stack when an opening paren is encountered and the topmost entry is
popped again when a closing paren is found.  When an error is found, the
topmost entry on the stack will be used to find the file related to the
error.

Anyway, don't you think you should get rid of all these overfull hbox
warnings?  Perhaps then the problem with the parser will go away.

Also, you can enable file:line:error messages in your TeX engine.  This
will most likely get rid of the problem.

-- 
Ralf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]