| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
Things like `<asdf>` shouldn't be highlighted.
|
|
|
|
Looks like I have to explicitly filter out whitespace. I can't rely on
`skipwhite` to do it for me.
|
|
Since `Up`, `Play`, and `Down` are also defined in
`domeKeySpecialKeyKeyword`, `domeKeyTriggerKeyKeyword` would never get
matched. Remove it since it doesn't get used. We already have the
`domeKeyDefinitionTrigger` matcher to restrict the possible trigger
keywords.
|
|
`domeKeyMapDefinitionAction` was taking over the trigger spot since
nothing in `domeKeyMapDefinitionTrigger` matched. Thanks vim-scriptease
for `zS` to show syntax groups under the cursor.
|
|
I guess this worked before for `map` lines because of the
`domeKeyDefinitionTrigger` matcher.
|
|
This matcher should be able to work in `map`, `cmd`, and `mode`.
|
|
This only works for `map` definitions, but I'll be using what I've
learned here for the other map types.
* Only highlight `map` if it's on the start of a line
* Only highlight `<Up>`, `<Play>`, and `<Down>` in map triggers
* Highlight any special key in map actions
|
|
Initial syntax highlighting definitions.
Highlights:
* Comments
* map, cmd, mode
* Special keys
Still some tricky sounding edge cases to handle, but this already takes
care of the basics very well.
|
