2 Apr 14:38 2010

## Re: 11.86; TeX-next-error opens a blank buffer when ) appears in a overful hbox.

* Nicolas Richard (2010-03-30) writes:

> When using TeX-next-error after compiling the following document,
> AUCTeX opens a blank buffer named "Web2C 7.5.7", instead of going to
> the point where the error occured in the current buffer.
[...]
> This is obviously caused by the character ')' which shows up in the log
> because of the overful box, but I don't know how to fix it. It also
> happens if you put '()' instead of just ')'.

I don't think there is much we can do here.  At least I don't see a way
to distinguish the closing parenthesis included in the overfull hbox
message from the parentheses marking file beginnings and ends.

What I'd like to try is to allow TeX-error-file' to become empty in
TeX-parse-error'.  That way we could at least get rid of the craziness
that is the opening of buffers on non-existent files.  Instead there
would be an error with the message "Error occured after last TeX file
closed".

Anyway, the canonical answer to problems with the error parser is to
enable file:line:error messages in LaTeX.  And with TeX Live you should
not lose anything from the error message (in contrast to MiKTeX).

--

--
Ralf


16 Apr 17:23 2010

### Re: 11.86; TeX-next-error opens a blank buffer when ) appears in a overful hbox.

Le 02/04/10 14:38, Ralf Angeli a écrit :
> Anyway, the canonical answer to problems with the error parser is to
> enable file:line:error messages in LaTeX.  And with TeX Live you should
> not lose anything from the error message (in contrast to MiKTeX).

Thanks, I'm now using that option[*] and it works... except when
TeX-debug-warnings is on and I'm trying to compile this:

\documentclass{minimal}
\begin{document}
$$aaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaa )$$
%\foo %% Uncommenting this avoids the problem by adding a true error.
\ref{foo}
\end{document}

Again, going to next error opens a new (blank) buffer, unless there is a
real error between the bad box and the warning (as obtained by
uncommenting \foo).

--

--
Nicolas

[*] Though i'm not sure I did it correctly, I have this :
(custom-set-variables '(LaTeX-command "latex -file-line-error"))


17 Apr 14:08 2010

### Re: Re: 11.86; TeX-next-error opens a blank buffer when ) appears in a overful hbox.

* Nicolas Richard (2010-04-16) writes:

> Le 02/04/10 14:38, Ralf Angeli a écrit :
>> Anyway, the canonical answer to problems with the error parser is to
>> enable file:line:error messages in LaTeX.  And with TeX Live you should
>> not lose anything from the error message (in contrast to MiKTeX).
>
> Thanks, I'm now using that option[*] and it works... except when
> TeX-debug-warnings is on and I'm trying to compile this:

[...]

Thanks for the test case.

> Again, going to next error opens a new (blank) buffer, unless there is a
> real error between the bad box and the warning (as obtained by
> uncommenting \foo).

Yes, these warnings are not issued in a file:line:error style, so here
we have the same problem as if this would not be enabled.  I don't think
there is much we can do to resolve this.  The development version of
AUCTeX now emits an error message instead of opening a blank buffer.
Not ideal, but more comprehensible for the user.

--

--
Ralf



Gmane