Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add support for defining cmd on a per-project level #11

Merged
merged 1 commit into from
Mar 18, 2016

Conversation

ajmichels
Copy link
Contributor

  • implements a custom cmd() method to check for the existence
    of an inline cmd setting
  • updated README documentation to show example of new functionality

closes #10

@ajmichels ajmichels force-pushed the per-project-executable branch from efd7755 to b056659 Compare March 12, 2016 01:48
@ajmichels ajmichels added this to the 1.1.0 milestone Mar 14, 2016
* implements a custom `cmd()` method to check for the existence
  of an inline `cmd` setting
* updated README documentation to show example of new functionality
* add message file for the next version of the package

closes SublimeLinter#10
@ajmichels ajmichels force-pushed the per-project-executable branch from b056659 to 296a402 Compare March 14, 2016 16:19
ajmichels added a commit that referenced this pull request Mar 18, 2016
add support for defining cmd on a per-project level
@ajmichels ajmichels merged commit e6f4c2b into SublimeLinter:master Mar 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Per-project executable setting
1 participant