World of Warcraft syntax highlight, auto-completion and global finder/highlighter for Sublime Text 2/3.
- Full API syntax highlighting for lua, xml and toc files.
- Highlight invalid/removed/deprecated API functions and events.
- Global finder build system, which finds any global variables with detailed information for the current lua file.
- Global highlighter and liter tool with SublimeLinter.
- Download the package, unzip it then remove the -master suffix, and copy the folder into your Sublime Text 2/3 Packages folder.
- Open any of the supported file and set the syntax for the selected file: WoWDevelopment -> WoW Lua, WoW TOC, WoW XML.
The autocomplete is based on scopes, so no settings are neccessary.
-
In Sublime Tools -> Build System -> Select Wow Global Finder.
-
Ctrl+B to run the system.
- Add a commented line in the lua file and list the globals with commas: -- GLOBALS: math, string, table
-
First install the SublimeLinter package.
-
Then add the path to luacheck.exe to your system PATH table, or to the paths/windows setting in the Sublime Linter settings: "c:\Users\UserName\AppData\Roaming\Sublime Text 3\Packages\WoWDevelopment\WoW Global Finder\"
-
Add "wow lua": "lua", to the syntax_map in the Sublime Linter settings.
-
In Sublime Tools -> SublimeLinter -> Toggle Linter then enable globalfinder and disable any other installed linters.
-
Restart Sublime.
- Add a commented line in the lua file and list the globals without commas: -- luacheck: globals math string table
Ignored globals:
- Global Functions: Reference\API Reference\API Reference (blizzard).sublime-completions.txt
- Global Booleans: Reference\Global Reference\Global Booleans.sublime-completions.txt
- Global Console Variables: Reference\Global Console Variables.sublime-completions.txt
- Global Numbers: Reference\Global Reference\Global Numbers.sublime-completions.txt
- Global Strings: Reference\Global Reference\Global Strings.sublime-completions.txt
If you would like to enable autocomplete for these, just change the .txt extension to: .sublime-completions.
Currently had I to roll back to using .sublime-snippet files instead of .sublime-autocomplete ones, since sublime currently has mutiple issues if any autocomplete files gets loaded for your current syntax. Hopefully it's gonna be fixed soon, and I can go back for autocomplete files to reduce the clutter.
Until then if you have any .sublime-completions file loaded for a syntax, then your buffer competions won't get shown up, and the fuzzy search for the completions brings up a lot more irrelevant hits, since it's also searing in the trigger descriptions.


