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
FYI, I defined a new grammar for a vscode extension here. IMHO, it allows for a better differentiation of keywords. For example, with the current syntax defined in this repo (but in vscode):
and with the grammar I defined:
This is an example with my color theme, but I generally define more specifically keywords. So it is a lot of small improvements, for example:
punctuation is defined
operators are defined
type and functions are differentiated
parameters of functions like dim, coef... are only defined when used like it. Example, in the current grammar, they are picked up everywhere so
I took care of it, it is a regular variable outside of function arguments:
They are still some improvements to do, but I think the new grammar allows for a better differentiation of keywords, and it is easy to add new function/type name in scopes named builtin-foo and the regex should be ok.
The text was updated successfully, but these errors were encountered:
And since all the editors like VSCode, atom, Sublime etc. use TextMate grammars, may be it would be better to centralised the .tmLanguage file in a repo and let repositories defining extensions for these editors refer to this centralised repository. So that you do not have to maintain yourself extensions for all these editors but just the grammar.
FYI, I defined a new grammar for a vscode extension here. IMHO, it allows for a better differentiation of keywords. For example, with the current syntax defined in this repo (but in vscode):
and with the grammar I defined:
This is an example with my color theme, but I generally define more specifically keywords. So it is a lot of small improvements, for example:
I took care of it, it is a regular variable outside of function arguments:
They are still some improvements to do, but I think the new grammar allows for a better differentiation of keywords, and it is easy to add new function/type name in scopes named
builtin-foo
and the regex should be ok.The text was updated successfully, but these errors were encountered: