Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maybe allow changing LaTeX distro for syntax highlighting? #3783

Open
Vivraan opened this issue Nov 30, 2024 · 1 comment
Open

Maybe allow changing LaTeX distro for syntax highlighting? #3783

Vivraan opened this issue Nov 30, 2024 · 1 comment
Labels
bug Deficiencies in TeXiFy behaviour. more-info-needed More information is needed from the person filing the issue. parser Issues for which significant changes in the parser are needed

Comments

@Vivraan
Copy link

Vivraan commented Nov 30, 2024

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:

\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

Expected behavior

No squiggles!

Actual behavior

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.

(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 💀

@Vivraan Vivraan added bug Deficiencies in TeXiFy behaviour. untriaged Issue type still needs to be triaged or verified. labels Nov 30, 2024
@PHPirates
Copy link
Collaborator

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?

image

@PHPirates PHPirates added more-info-needed More information is needed from the person filing the issue. and removed untriaged Issue type still needs to be triaged or verified. labels Dec 1, 2024
@PHPirates PHPirates added the parser Issues for which significant changes in the parser are needed label Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Deficiencies in TeXiFy behaviour. more-info-needed More information is needed from the person filing the issue. parser Issues for which significant changes in the parser are needed
Projects
None yet
Development

No branches or pull requests

2 participants