Re: Avoid opening a buffer showing origin of an error (or warning) from \PackageError (Warning)

[jfbu]

Hello Ikumi Keita,

Le 01/08/2024 à 11:50, Ikumi Keita a écrit :
> Hi Jean, sorry for late answer.

Sorry as well for my late reply ;-)
> > > > > > jfbu <jfbu@free.fr> writes:
> > Presumably this is what AUCTeX knows already to do,
> > and anyhow the simplest could be to keep current code
> > but by default add to it a check whether
> > the-file-where-lies-the-offending-error is in
> > current directory and display it only then, except
> > if some
> > customizable option "always-go-to-error-originating-file"
> > has been made use of.
>
> I'm not sure whether I understand what you hope, but did you enable
> `TeX-error-overview-open-after-TeX-run' option? If not, please try and
> see whether it meets your need or not.

It is not exactly the feature asked-for but does go a long way.

I report a slight glitch:

----
LaTeX errors in ‘*~/Downloads/testauc output*’. Use C-c ` to display.
C-c ` is undefined
----

Indeed the focus is on the error overview frame, where C-c ` is
undefined.

One has to reput the focus on the document to have C-c ` work (and do
then what I want to avoid when error originates in external file).

My try was with

----
\documentclass{article}
\usepackage{unicode-math}
\begin{document}

\end{document}
----

and engine left to default.

Thanks to advice I will perhaps set TeX-error-overview-open-after-TeX-run
to t in my customization.  But in case errors do originate in
original compiled source this adds a layer, and there is this problem
that C-c ` does not work as one has to bring back the focus on
the original frame.

Best,

Jean-François

> Regards,
> Ikumi Keita
> #StandWithUkraine #StopWarInUkraine
> #Gaza #StopMassiveKilling #CeasefireNOW