Significant parser slowdown for Latex with complex parameters
See original GitHub issueIf I open the source of the tkz-tab package, the parser seems to get stuck (might be an infinite loop) on parsing some strict-keyval-pair. Perhaps you can have a look? You can find the file in your local latex distribution or at https://github.com/tkz-sty/tkz-tab/blob/master/latex/tkz-tab.sty

_Originally posted by @PHPirates in https://github.com/Hannah-Sten/TeXiFy-IDEA/issues/2388#issuecomment-1155312622_
Issue Analytics
- State:
- Created a year ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Improve formatter performance for TeX Live full #2433 - GitHub
I have a problem editing Latex file when both Texify and IdeaVim plugins are ... Significant parser slowdown for Latex with complex parameters...
Read more >Spacing around inline equations - TeX - LaTeX Stack Exchange
What is the parameter determining spacing and stretchability around inline equations? I want to tweak spacing exactly but cannot find where ...
Read more >The stringstrings Package - CTAN
Abstract. The stringstrings package provides a large and sundry array of routines for the manipulation of strings. The routines are developed not only...
Read more >Why does Tex/Latex not speed up in subsequent runs?
I've got 100 page manual that compiles in about second if I pass [draft] to {graphicx}, otherwise it takes about a minute. As...
Read more >Interactive Editing of MathML Markup Using TEX Syntax∗
may slow down the editing process because they of- ... can be extremely difficult. As long as insert oper- ... to deal with...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I don’t know what would be best, but I would appreciate if you could have a look into external rules. Yeah no hurries, I have to do a quick fix for this particular issue anyway, it’s just a matter of trying to prevent a stuck parser in the future which can be triggered by any update of any texlive package.
I think the unintuitive API could be alleviated somewhat by then parsing the key-value pairs at application level manually and then providing all the extension functions to replace the parser information - I think this would be the fallback solution if external rules don’t work out, as it’s probably the same code but then less nicely integrated with the parser.
I should note that the user story right now is that because we have sty files included in the LatexIndexableSetContributor, all these files will be parsed and hence if the parser gets stuck on one of them, the indexing gets stuck.
Parsing all these files was never the intention (though perhaps a nice test for the parser…) because it’s very slow and unnecessary (since our indexers are regex-based) and clutters the stub indices (#2433), so I will try to fix that before the next release anyway.