SublimeLinter 3 must be installed in order to use this plugin. If SublimeLinter 3 is not installed, please follow the instructions here.
Before using this plugin, you must ensure that
abcm2ps is installed on your system. To install
abcm2ps, do the following:
abcm2psby typing the following in a terminal:
<package manager> install abcm2ps
Note: This plugin requires
abcm2ps version or later.
In order for
abcm2ps 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
abcm2ps, you can proceed to install the SublimeLinter-contrib-abcm2ps 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
abcm2ps. Among the entries you should see
SublimeLinter-contrib-abcm2ps. If that entry is not highlighted, use the keyboard or mouse to select it.
In addition to the standard SublimeLinter settings, SublimeLinter-contrib-abcm2ps provides its own settings. Those marked as "Inline Setting" or "Inline Override" may also be used inline.
|Setting||Description||Inline Setting||Inline Override|
If you would like to contribute enhancements or fixes, please do the following:
- Fork the plugin repository.
- Hack on a separate topic branch created from the latest
- Commit and push the topic branch.
- Make a pull request.
- Be patient. ;-)
Please note that modifications should follow these coding guidelines:
- Indent is 4 spaces.
- Code should pass flake8 and pep257 linters.
- Vertical whitespace helps readability, don’t be afraid to use it.
- Please use descriptive variable names, no abbreviations unless they are very well known.
Thank you for helping out!