bug#63228: 13.2.0; TeX-auto-generate-global TeX-auto-parse-region: Wrong type argument: stringp, nil

[Arash Esbati]

"Sebastian Drude" <drude@xs4all.nl> writes:

> I am using the Language Science Press (for xetex) langscibook class,
> and when starting, I could not complement on commands defined in that
> class and other packages loaded in a local file
> \input{localpackages.tex}.  I had to update langscibook, and after
> that I thought I should create the AUCTeX style files for my packages,
> which is when I started to try to invoke TeX-auto-generate-global.

Yes, AUCTeX doesn't have a style file for langscibook.cls, but that
might change.

> So you tell me that invoking TeX-auto-generate-global is actually not
> necessary?  But as far as I can see, the AUCTeX-style-files do cover
> only a part of all packages provided with LiveTeX.

No, AUCTeX doesn't have a style file for every package provided by
TeXlive.  Usually, people write a style file for packages and they are
then submitted to AUCTeX.  For a somewhat complicated class like
langscibook.cls, you should write a support file manually.
`TeX-auto-generate-global' would always produce suboptimal results.
Please find attached my 10 minutes take on such a file; I admit I
couldn't find and/or grasp the manual.  So maybe you want to take over,
make it complete and submit it to AUCTeX.  You can save this file in a
directory which is part of `TeX-style-private' and then restart AUCTeX,
and be sure you have set `TeX-parse-self' to t in your init file.

langscibook.el
Description: application/emacs-lisp

> And So it is normal that it fails on so many files with the error
> "TeX-auto-parse-region: Wrong type argument: stringp, nil"?  This
> seems very weird to me...

Usually not, and I'm seeing this for the first time, but to be honest,
I'm not willing to debug it.

> yes, I used `M-x list-packages RET', searched for AUCTeX with C-s, and
> then entered the package and chose "install".  I am not sure whether I
> saw the "obsolete" description the first time I searched for the
> package or only the second time.

Is it still present?

Best, Arash