SublimeLinter plugin for the CorvisaCloud Summit platform
- Total 96K
- Win 49K
- Mac 28K
- Linux 20K
|Jun 3||Jun 2||Jun 1||May 31||May 30||May 29||May 28||May 27||May 26||May 25||May 24||May 23||May 22||May 21||May 20||May 19||May 18||May 17||May 16||May 15||May 14||May 13||May 12||May 11||May 10||May 9||May 8||May 7||May 6||May 5||May 4||May 3||May 2||May 1||Apr 30||Apr 29||Apr 28||Apr 27||Apr 26||Apr 25||Apr 24||Apr 23||Apr 22||Apr 21||Apr 20||Apr 19|
This linter plugin for SublimeLinter provides an interface to Corvisa LLC's SummitEditor through
luacheck. It will be used with files that have the “Lua (Summit)” syntax.
SublimeLinter 3 must be installed in order to use this plugin. If SublimeLinter 3 is not installed, please follow the instructions here. SummitEditor must also be installed. If it is not installed, follow the instructions.
Before using this plugin, you must ensure that
luacheck is installed on your system. To install
luacheck, follow the instructions.
lua to be installed.
In order for
luacheck to be executed by SublimeLinter, you must ensure that its path is available to SublimeLinter. Before going any further, please read and follow the steps in “Finding a linter executable” through “Validating your PATH” in the documentation.
Once you have installed and configured
luacheck, you can proceed to install the SummitLinter plugin if it is not yet installed.
Please use Package Control to install the linter plugin. This will ensure that the plugin will be updated when new versions are available. If you want to install from source so you can modify the source code, you probably know what you are doing so we won’t cover that here.
To install via Package Control, do the following:
Within Sublime Text, bring up the Command Palette and type
install. Among the commands you should see
Package Control: Install Package. If that command is not highlighted, use the keyboard or mouse to select it. There will be a pause of a few seconds while Package Control fetches the list of available plugins.
When the plugin list appears, type
SummitLinter. Among the entries you should see
SummitLinter. If that entry is not highlighted, use the keyboard or mouse to select it.
For general information on how SublimeLinter works with settings, please see Settings. For information on generic linter settings, please see Linter Settings.
In addition to the standard SublimeLinter settings, SummitLinter provides its own settings adapted from the
luacheck settings. Those marked as “Default Setting" have their own setting in SublimeLinter's user settings for
summitlinter. Those not marked as “Default Setting” go in the
args list in SublimeLinter's user settings for
||Do not check for accessing global variables.|
||Do not check for redefined variables.|
||Do not check for unused variables.|
||Do not check for unused arguments and loop variables.|
||Do not check for unused values.|
||Adjust globals for Lua 5.1/5.2 compatibility.|
||Do not be _ENV-aware.|
||Do not report warnings related to these variables||✓|
||Only report warnings related to these variables||✓|
||Exit with 0 if there are <limit> or less warnings.||✓|
||Suppress output for files without warnings.
Settings marked as “Default Setting” may also be used inline as per SublimeLinter's documentation. Since, by default,
require are pre-defined as
globals, using the
globalssetting inline requires you to include
require again in addition to any other settings. For example:
-- [SublimeLinter summitlinter-globals:channel,require,foo] will maintain default behavior while adding
foo as a global. This follows for any default settings saved in SublimeLinter's user settings as well. For example, if
"ignore": "foo" is in your user settings, using
ignore to ignore
bar inline (while continuing to ignore
foo) would require the following:
-- [SublimeLinter summitlinter-ignore:foo,bar].