tobil4sk

If it is a property access identifier, it will be treated as a keyword, otherwise as a literal.

Editors may not want to mark all of them with `@keyword`, for example [neovim](https://neovim.io/doc/user/treesitter.html#_treesitter-syntax-highlighting) provides more specific groups such as `@keyword.modifier` etc. so it is better to let the highlights.scm...

All these cases cause parser errors due to the `pack.Test`: ```haxe class Main extends pack.Test {} class Main implements pack.ITest {} interface Main extends pack.Test {} ``` They all give:...

Current version was causing this error: ``` Download https://registry-staging.deno.com/@std/path/meta.json WARN Failed fetching https://registry-staging.deno.com/@std/path/meta.json. Retrying in 250ms... WARN Failed fetching https://registry-staging.deno.com/@std/path/meta.json. Retrying in 500ms... WARN Failed fetching https://registry-staging.deno.com/@std/path/meta.json. Retrying in 1000ms......

Allow using vim theme as base if running on neovim

2

Add the 'neovim_legacy_compat' option for colorschemes so that they can use the old vim theme as a base. Vim themes that do not provide full neovim support can use this...

Without this, there is no way to use `IGrammar.tokenizeLine2` without redefining the EncodedTokenDataConsts and reimplementing the functions. See for example: https://github.com/microsoft/vscode/blob/8810d514c7452ce912bd9bc6f79a3429cc55dcdd/src/vs/editor/common/encodedTokenAttributes.ts#L101-L103

Follow up to #284.

Whitespace before type parameter list breaks parsing

2

The syntax does not accept type parameters if there is a space before `/ + \ start=// \ contains=@typescriptType \ nextgroup=typescriptFuncCallArg,@typescriptTypeOperator \ contained skipwhite ```