Open Vivraan opened 2 days ago
PyCharm 2024.3 (Professional Edition) Build #PY-243.21565.199, built on November 13, 2024.
Edition Windows 11 Home Version 23H2 Installed on 28-09-2022 OS build 22631.4541 Experience Windows Feature Experience Pack 1000.22700.1055.0
0.9.8 stable
I used old-style syntax (\document and \enddocument) which didn't throw, but which isn't valid XeLaTeX.
\document and \enddocument
Below, \end gets a squiggle.
\end
Use this in main.tex:
main.tex
\documentclass{article} % ... \begin{document} \renewcommand{\familydefault}{\rmdefault} \captionsetup{font=tiny} \input{titlepage} \input{headerfooter} \tableofcontents \pagebreak \input{acronyms} \pagebreak % % % % % % % % % % % % % % % % % % % % % % % % % REPORT CONTENT % % % % % % % % % % % % % % % % % % % % % % % % % % \fontsize{9}{11}\selectfont{ \input{v0.0.3/report} } \pagebreak \printbibliography \end{document} %^~~ unremovable red squiggle
No squiggles!
Yes squiggles with error:
<no math content>, <parameter> or LatexTokenType.* expected, got '\end'
This suggests that the internal distro server isn't able to parse this.
N/A
I'm happy to contribute on this but I have a deadline today that will end my career haha 💀
That is indeed a parser error, however the example you gave doesn't result in the error for me. I also don't see anything unexpected. Could you double check if the example reproduces the problem?
Type of JetBrains IDE (IntelliJ, PyCharm, etc.) and version
PyCharm 2024.3 (Professional Edition) Build #PY-243.21565.199, built on November 13, 2024.
Operating System
Edition Windows 11 Home Version 23H2 Installed on 28-09-2022 OS build 22631.4541 Experience Windows Feature Experience Pack 1000.22700.1055.0
TeXiFy IDEA version
0.9.8 stable
What I did (steps to reproduce)
I used old-style syntax (
\document and \enddocument
) which didn't throw, but which isn't valid XeLaTeX.Minimal example to reproduce the problem
Below,
\end
gets a squiggle.Use this in
main.tex
:Expected behavior
No squiggles!
Actual behavior
Yes squiggles with error:
This suggests that the internal distro server isn't able to parse this.
(if applicable) The full stacktrace of the exception thrown
N/A
I'm happy to contribute on this but I have a deadline today that will end my career haha 💀