"! Undefined control sequence. <argument> \fail" after update. But what package?

[David Carlisle]

On Thu, 6 Jan 2022 at 20:10, Don Hosek <don.hosek at gmail.com> wrote:

> > As your document errors in the preamble, providing an MWE is really
> > easy. At least provide the full log until the error so that one has
> > at least a chance to identify the package.
>
> It occurs to me that the means by which TeX identifies the location of an
> error is not so great when many input files are involved (especially with
> nested \input commands). Perhaps there should be a change to the output[1]
> of an error location from
>
> > l.112   {}{\fail}
>
> to
>
> > file.tex: l.112   {}{\fail}
>

that is already available as --file-line-error  command line option in all
texlive engines.

David


> We can do this by modifying s.313 so that it does:
>
> > print(input_stack[base_ptr].name_field); print_nl(“l.”); print_int(line);
>
> instead of
>
> > print_nl(“l.”); print_int(line);
>
> Unless there’s some compelling reason not to, this seems like something
> that could/should have been done long ago.
>
> -dh
>
> ——
>
> 1. I had originally thought that this would need to be an eTeX extension
> but I see that Knuth writes:
>
> > This routine should be changed, if necessary, to give the best possible
> indication of where the current line resides in the input file.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/tex-live/attachments/20220106/e5990390/attachment.html>