ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Sublime​Linter-contrib-dmd

by veelo ST3

SublimeLinter plugin for the D programming language using dmd

Details

Installs

  • Total 55
  • Win 32
  • OS X 7
  • Linux 16
Nov 18 Nov 17 Nov 16 Nov 15 Nov 14 Nov 13 Nov 12 Nov 11 Nov 10 Nov 9 Nov 8 Nov 7 Nov 6 Nov 5 Nov 4 Nov 3 Nov 2 Nov 1 Oct 31 Oct 30 Oct 29 Oct 28 Oct 27 Oct 26 Oct 25 Oct 24 Oct 23 Oct 22 Oct 21 Oct 20 Oct 19 Oct 18 Oct 17 Oct 16 Oct 15 Oct 14 Oct 13 Oct 12 Oct 11 Oct 10 Oct 9 Oct 8 Oct 7 Oct 6 Oct 5
Windows 1 4 0 0 0 1 0 1 1 2 1 1 0 1 1 2 5 6 9 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
OS X 0 0 0 0 0 0 0 0 1 1 1 1 0 1 0 0 0 2 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 0 0 1 0 2 1 0 0 0 2 0 0 2 3 1 5 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

SublimeLinter-contrib-dmd

Build Status

This linter plugin for SublimeLinter provides an interface to dmd, the reference compiler for the D programming language. It will be used with files that have the “D” syntax. These will be parsed by dmd and any errors and warnings will be shown inline and optionally as tooltips. The advantages to pure syntax linters are:

  1. The parser is always up-to-date.
  2. Does full symbol resolution, including imports.
  3. Mixins are expanded.
  4. Templates are validated.
  5. Deprecation warnings are included.
  6. The “did you mean …” assistance appears right where it is most helpful.

warningserrors

Installation

SublimeLinter 3 must be installed in order to use this plugin. If SublimeLinter 3 is not installed, please follow the instructions here.

Linter installation

Before using this plugin, you must ensure that dmd is installed on your system. To install dmd, go to https://dlang.org/download.html.

Note: This plugin was developed using dmd 2.076.1.

Linter configuration

In order for dmd 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 dmd, you can proceed to install the SublimeLinter-contrib-dmd plugin if it is not yet installed.

Plugin installation

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:

  1. 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.

  2. When the plugin list appears, type dmd. Among the entries you should see SublimeLinter-contrib-dmd. If that entry is not highlighted, use the keyboard or mouse to select it.

Settings

This plugin looks for DUB project configuration files in open folders and adds any required import paths that can be determined from those automatically. It is possible to pass additional arguments to dmd using a setting.

For general information on how SublimeLinter works with settings, please see Settings. For information on generic linter settings, please see Linter Settings.

You may pass any arguments and switches to dmd by configuring the args linter setting, like so:

"dmd": {
                "@disable": false,
                "args": ["-I/my/additional/include/dir", "-dip25"],
                "excludes": []
            }

Contributing

If you would like to contribute enhancements or fixes, please do the following:

  1. Fork the plugin repository.
  2. Hack on a separate topic branch created from the latest master.
  3. Commit and push the topic branch.
  4. Make a pull request.
  5. Be patient. ;-)

Please note that modifications should follow these coding guidelines:

  • Indent is 4 spaces.
  • Code should pass flake8 and pydocstyle 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!