emacs-auctex 拒绝打开 .tex 文件
安装 emacs 28.1 和 auctex 13.1 后，我无法再打开 .tex 文件。
如果我在 emacs Ctrl-x -f Blau-2022-03-20.tex 中输入，我会收到
Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
replace-regexp-in-string("\[ \\11\\15\\n%\]" "" nil)
LaTeX-xparse-macro-parse(mac)
LaTeX-xparse-auto-cleanup()
run-hooks(TeX-auto-cleanup-hook)
TeX-auto-parse()
run-hooks(TeX-update-style-hook)
TeX-update-style(t)
#f(compiled-function () #\<bytecode -0x12260f12797895d8\>)()
run-hooks(find-file-hook)
after-find-file(nil t)
find-file-noselect-1(#\<buffer Blau-2022-03-20.tex\> "\~/Desktop/Eigene Dokumente/Briefe/Blau- 2022-03-20...." nil nil "\~/Desktop/Eigene Dokumente/Briefe/Blau-2022-03-20...." (790801 2051))
find-file-noselect("\~/Desktop/Eigene Dokumente/Briefe/Blau-2022-03-20...." nil nil t)
find-file("\~/Desktop/Eigene Dokumente/Briefe/Blau-2022-03-20...." t)
funcall-interactively(find-file "\~/Desktop/Eigene Dokumente/Briefe/Blau-2022-03-20...." t)
call-interactively(find-file nil nil)
command-execute(find-file)
根本无法打开文件的信息。如果我单击四个点，就会出现 .tex。
顺便说一句：它适用于 .tex~ 文件。
我不知道我可以尝试什么，它已经工作了几十年......
这个问题自 2014 年以来就有人提出，但我发现的所有解决方案都不适合我。
PS：如果我第二次输入myfile.tex，它就会起作用。因此，在 Ctr-x -f myfile.tex 之后，我收到了奇怪的消息，但在另一个 Ctr-x -f myfile.tex 之后，我可以像往常一样打开该文件。
After installing emacs 28.1 and auctex 13.1 I can't open .tex-files any longer.
If I enter in emacs Ctrl-x -f Blau-2022-03-20.tex I get
Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
replace-regexp-in-string("\[ \\11\\15\\n%\]" "" nil)
LaTeX-xparse-macro-parse(mac)
LaTeX-xparse-auto-cleanup()
run-hooks(TeX-auto-cleanup-hook)
TeX-auto-parse()
run-hooks(TeX-update-style-hook)
TeX-update-style(t)
#f(compiled-function () #\<bytecode -0x12260f12797895d8\>)()
run-hooks(find-file-hook)
after-find-file(nil t)
find-file-noselect-1(#\<buffer Blau-2022-03-20.tex\> "\~/Desktop/Eigene Dokumente/Briefe/Blau- 2022-03-20...." nil nil "\~/Desktop/Eigene Dokumente/Briefe/Blau-2022-03-20...." (790801 2051))
find-file-noselect("\~/Desktop/Eigene Dokumente/Briefe/Blau-2022-03-20...." nil nil t)
find-file("\~/Desktop/Eigene Dokumente/Briefe/Blau-2022-03-20...." t)
funcall-interactively(find-file "\~/Desktop/Eigene Dokumente/Briefe/Blau-2022-03-20...." t)
call-interactively(find-file nil nil)
command-execute(find-file)
an can't open the file at all. If I click on the four dots, .tex appears.
BTW: It works with .tex~-files.
I have no idea what I could try, it worked for decades...
The question has been asked since 2014, but all solutions I found didn't work for me.
PS: It works if I enter myfile.tex for a second time. So after Ctr-x -f myfile.tex I get the strange message, but after another Ctr-x -f myfile.tex I can open the file as usual.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我遇到了一个类似的问题，这使我分心。
最后，我发现错误消息具有误导性。我正在使用Mac，该文件位于MS OneDrive文件夹中。我没有该文件的本地副本，也没有OneDrive运行。当我在大量浪费时间后意识到问题时，我打开了OneDrive，完全有您的症状 - 第一次，我收到了错误消息，第二次起作用。我的假设是我第一次这样做时，文件不在那里，因此错误消息，但它促使文件下载，并且在该文件第二次存储在本地并起作用。
I ran into a similar problem which drove me to distraction.
In the end, I discovered that the error message was misleading. I'm using a Mac and the file was in a MS OneDrive folder. I didn't have a local copy of the file and I didn't have OneDrive running. When I realised the problem after much wasting of time, I turned on OneDrive and had exactly the symptom you had -- first time, I got the error message, and second time it worked. My hypothesis is that the first time I did this, the file was not there hence the error message, but it prompted download of the file, and by the second time the file was stored locally and it worked.