-
Notifications
You must be signed in to change notification settings - Fork 142
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
how do I write my own syntax? #475
Comments
Yes: http://www.sublimetext.com/docs/scope_naming.html http://www.sublimetext.com/docs/selectors.html
It's generally assumed that syntaxes are written for Sublime Text or Sublime Merge, as opposed to directly for There's also some tips at sublimehq/Packages#757, but they assume you already know the basics. If you prefer tutorial videos, @OdatNurd has done a great job covering all of these concepts. I'm not sure about a specific video to link to, but one/some of these may be a good starting point: https://www.youtube.com/@OdatNurd/search?query=syntax |
Scope naming is exactly what I needed. Thank you. Very great to see that you take a lot of care maintaining syntect 😃 |
So I'll close this then. Thank you :) |
It is not really clear how I can write my own syntaxes start to finish for use with syntect. I have the regexes I need to figure out what needs to be highlighted where, but I do not know how to make these into a
.sublime-syntax
file that will work with syntect. For one thing, I see in the Sublime docs that definitions generally look like this:How does syntect know that the
keyword.control.c
scope needs to be highlighted as any color in particular? Does the color theme have some sort of marking forkeyword.control.*
that will highlight any statement with a givenScope
as long as it starts withkeyword.control.*
?The docs explain quite well how to load and manipulate syntaxes, but they don't say anything about how to write them.
The text was updated successfully, but these errors were encountered: