Skip to content

Commit

Permalink
Adds sublime-jshint editor link to README
Browse files Browse the repository at this point in the history
sublime-jshint build recently switched to using node-jshint instead of OS native libraries.
  • Loading branch information
Jamie Hoover ⚔ committed Feb 17, 2012
1 parent 8b3115a commit 333bfed
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion README.md
Expand Up @@ -4,7 +4,7 @@ A command line interface and npm package for jshint.

## Install

To use jshint from any location (for npm v1.x) you need to install using the global (-g) flag.
To use jshint from any location (for npm v1.x) you need to install using the global (-g) flag.

npm install -g jshint

Expand All @@ -24,6 +24,7 @@ Note: If you are using npm v1.x be sure to install jshint locally (without the -

* [gedit-node-jshint](https://github.com/niftylettuce/gedit-node-jshint) - Simply use CTRL+J in gedit to run JSHint using `node-jshint`.
* [vim syntastic](https://github.com/scrooloose/syntastic) - Run node-jshint at each file save.
* [sublime-jshint](https://github.com/uipoet/sublime-jshint) - `F7` or `command-B` on any .js file. `F4` next error line,column. `shift-F4` previous error line,column.

## Custom Reporters

Expand Down

0 comments on commit 333bfed

Please sign in to comment.