Nikos M.

Try sth like: ```javascript "keyword": {"autocomplete":["если"],"tokens":[ "RE::/^(если)\\s/" // do similar for other keyword tokens ]} ``` or try using unicode codes in regular expressions instead of the actual characters. You...

This is an option I am considering for many of my open-source projects. The most important part is dependency handling which npm can handle better, but as an alternative untill...

I dont use typescript, I dont have a case where I need it, plain javascript is fine, as far as I can eliminate any unnecesary internediate/compilation step I am happy....

This is a valid point. Even though 3rd-party libs dont have to be coded in typescript to work inside another project. It is simply vanilla js, it works. I dont...

Please see comments on [this pull request](https://github.com/foo123/editor-grammar/pull/8) and suggestions to quickly resolve your problem untill I make these adjustments myself some time in the future

I'm not sure I understand what the problem is. But in any case you can define the tokens like the following (simpler): ```javascript "var": "RE::/var\\b/i", "eq": "=", "sub": "RE::/[A-Za-z$][A-Za-z0-9$]*/" ```...

@wangliabc , Please write in english, I am not a speaker of Chinese (although I would like to learn) According to google translation you ask something about case sensitivity of...

@joshgoebel as long as there are ways to bypass the default tokenizer and there is a way to provide the actual token (parsed with an external parser), my addon is...

Check out this addon https://github.com/foo123/highlightjs-grammar which works for all syntax highlighters and enables you to define a grammar specification for a language and use it as is in every highlighter...

@yyyc514 of course you have a point in that grammars need to be written themselves, else it would be good if a repository of grammars exists. I dont mind having...