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
Atom 1.25 came out today, and with that is a new opt-in parser for syntax highlighting called tree-sitter.
Instead of doing regexes on each line of code, it actually parses the whole document, which means it's performant on long lines (which would fix #139), and it's also faster than the current method of syntax highlighting, which is helpful when working with large LaTeX documents.
Thanks for reaching out us, and we also recognize how powerful tree-sitter can be. That being said, each parser library is a Node.js library separated from Atom package of the associated language and yitzchak/tree-sitter-latex is being developed.
We have no plan to create our own parser, but will definitely consider adding tree-sitter support once tree-sitter-latex is published to npm.
@Aerijo@yudai-nkt I am currently a little busy with some other projects so if either of you is interested in picking up where I left off on yitzchak/tree-sitter-latex please let me know.
Atom 1.25 came out today, and with that is a new opt-in parser for syntax highlighting called tree-sitter.
Instead of doing regexes on each line of code, it actually parses the whole document, which means it's performant on long lines (which would fix #139), and it's also faster than the current method of syntax highlighting, which is helpful when working with large LaTeX documents.
This does mean creating a new file with rules that describe the language, according to this documentation.
I might be willing to take a stab at writing this (though I might not get too far since I'm LaTeX is rather complex).
The text was updated successfully, but these errors were encountered: