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

Incorrect code style for paths/comments in tikzpicture environment #3840

Open
xchatiii opened this issue Jan 4, 2025 · 1 comment
Open
Labels
bug Deficiencies in TeXiFy behaviour. parser Issues for which significant changes in the parser are needed

Comments

@xchatiii
Copy link

xchatiii commented Jan 4, 2025

Environment

IntelliJ IDEA 2024.3.1.1 (Ultimate Edition) on Windows and TeXiFy IDEA 0.9.9.

Image explains everything

{6BB8B6D8-2460-4B61-B387-A7E83C67EF15}

Comments are not in the right code style (for me, a gray color).
It seems like the space (highlighted by the cursor) is being used as a delimiter?

{AC821060-D7C5-462B-93BD-2710E36AD058}

(I indent my code with tab characters)
If there is another space that "terminates the space", everything is proper again except that putting the cursor at \path highlights a rather arbitrary part.

{DFF2771D-C14C-4012-A512-B36E3AA8B199}

@xchatiii xchatiii added bug Deficiencies in TeXiFy behaviour. untriaged Issue type still needs to be triaged or verified. labels Jan 4, 2025
@PHPirates
Copy link
Collaborator

Thanks for reporting this! I can reproduce the issue, looks like I made a mistake in the lexer which makes it parse something in this example as verbatim text.

\begin{tikzpicture}
	\path (0,0)--(1,0);
\some\commands
	% Highlighting wrong here
\end{tikzpicture}

@PHPirates PHPirates added parser Issues for which significant changes in the parser are needed and removed untriaged Issue type still needs to be triaged or verified. labels Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Deficiencies in TeXiFy behaviour. parser Issues for which significant changes in the parser are needed
Projects
None yet
Development

No branches or pull requests

2 participants