tridactyl / vim-tridactyl

VIM syntax plugin for Tridactyl configuration files

vim-tridactyl

VIM syntax plugin for Tridactyl configuration files.

Installation

Install with your favorite VIM plug manager. E.g. for vim-plug:

Plug 'tridactyl/vim-tridactyl'

vim-tridactyl's Issues

Fix allowed symbols in commands

I started matching ex commands with the list of predefined ones (not including default aliases). These names ale all alpha letters, a couple than have numbers, and few more that have underscores. I'm currently allowing that character range for user defined commands and aliases, but I see we have at least one exception to account for: exclaim is aliased to !.

That opens the can of worms that I'm not sure which symbols should be allowed in command names. What else might be allowed? Dashes? Other symbols? What should I account for?

@bovine3dom perhaps you can point me in the right direction...

Catch pre-commands such as 'composite'

A number of commands function differently than others in that they immediately chain to new commands.

Examples:

• composite
• fillcmdline

Find keywords for 'set' family of commands

Find a list of keywords allowed by set, setgui (and their *_quiet friends) and match them following those commands.

Examples:

• tabstoolbar
• theme
• configversion

Include CSS highlighting for selectors

Many rules have trailing CSS selectors such as hint -xx <css_selector>. We should be able to import CSS rules and apply them to these pretty easily as long as they are always the last thing on the line and we know when to expect them.

Catch command flags

Many commands have -x or --x=y style command arguments that are passed before their usual expected data.

Catch these as appropriate. For example right now unbind expects a key sequence, but the next argument might actually be --mode=ex. Or js expects javascript, but it might actually get an arg -p first.