You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently I find on GitHub.com, in rendered markdown, in a fenced code block highlighted with tex language (```tex), if the previous line contains TeX comment (% followed by none or more characters), then the first command on current line is not recognized as TeX command any more.
But if current line contains leading space(s), then the highlighting for first command is repaired.
Maybe that's controlled by other repositories, for instance https://github.com/github/markup. But the most recent commit in that repo was two months ago...
The text was updated successfully, but these errors were encountered:
muzimuzhi
changed the title
First command is not recognized if last line ends with comment
First TeX command is not recognized if last line contains comment
Dec 28, 2023
Thank you for the bug report. I do not think the problem you describe has anything to do with the updates to the TeX grammar in this Bundle. At least in TextMate everything seems to work as expected. I tried the following:
Open TextMate
Create a new file (⌘ + N)
Change the syntax to TeX: Choose “TeX” in the second column of the status bar
Past the following text:
\relax \relax
%
\relax \relax
%
\relax \relax
You can see the output on my machine in the following screenshot:
Recently I find on GitHub.com, in rendered markdown, in a fenced code block highlighted with
tex
language (```tex
), if the previous line contains TeX comment (%
followed by none or more characters), then the first command on current line is not recognized as TeX command any more.But if current line contains leading space(s), then the highlighting for first command is repaired.
The only change made to the most recent release of https://github.com/github-linguist/linguist (see github-linguist/linguist#6627) was my three commits that altered list of TeX primitives (8e47254...0be3da8). They are most likely the culprit, but I can't find the reason.
Maybe that's controlled by other repositories, for instance https://github.com/github/markup. But the most recent commit in that repo was two months ago...
The text was updated successfully, but these errors were encountered: