Closed u-fischer closed 3 years ago
as noted in an answer in stackexchange, we could adjust the definition of \ch@ck
in etex to avoid this error, although etex.sty only re-instates the original definition for other packages that may be using it, so this isn't clearly safe.
Alternatively we could guard kernel uses of \ch@ck
by a \relax
after the 3rd argument so the 4-argument form is harmless.
But I'm tempted to say this is a document error, no old documents can have
\begin{filecontents}[overwrite]
and no new documents should have \usepackage{etex}
looks as this has been resolve by some change, the example no longer errors for me.
from https://tex.stackexchange.com/questions/514498/beginfilecontentstabelle-tex-will-not-overwrite-existing-file
gives at the second compilation, when filecontents tries to overwrite the file