Closed audinue closed 2 months ago
This feels like the wrong place for this. I would think these keywords should be defined near where we define things like for
and throw
.
FWIW, I also wanted this feature. Since this seems like the PR will no go forward, so I thought I would post my workaround here:
When the document opens, change the name: to something different, e.g. name: CoffeeScript Custom
In contexts: main: add the lines
contexts:
main:
...
- match: '\b(import|as|from|export)\b'
scope: keyword.operator.coffee
I would be happy to merge in a PR that adds support for the missing keywords, but they should be defined in the proper place in the file. They shouldn’t be overloading debugger
.
This pull request adds
import
,as
,from
andexport
tokeyword.other.coffee
inCoffeeScript.tmLanguage
.