Skip to content

Commit 51a8f42

Browse files
committed
Update readme
1 parent 8276c4f commit 51a8f42

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

README.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
SublimeLinter-contrib-htmlhint
22
================================
33

4-
[![Build Status](https://travis-ci.org/SublimeLinter/SublimeLinter-contrib-htmlhint.svg?branch=master)](https://travis-ci.org/SublimeLinter/SublimeLinter-contrib-htmlhint)
4+
<!--- [![Build Status](https://travis-ci.org/SublimeLinter/SublimeLinter-contrib-htmlhint.svg?branch=master)](https://travis-ci.org/SublimeLinter/SublimeLinter-contrib-htmlhint) -->
55

66
This linter plugin for [SublimeLinter][docs] provides an interface to [htmlhint](https://github.com/mmaday/SublimeLinter-contrib-htmlhint). It will be used with files that have the “HTML” syntax.
77

@@ -11,14 +11,16 @@ SublimeLinter 3 must be installed in order to use this plugin. If SublimeLinter
1111
### Linter installation
1212
Before using this plugin, you must ensure that `htmlhint` is installed on your system. To install `htmlhint`, do the following:
1313

14-
1. Install Other.
14+
1. Install [Node.js](http://nodejs.org) (and [npm](https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager) on Linux).
1515

1616
1. Install `htmlhint` by typing the following in a terminal:
1717
```
1818
npm install -g htmlhint
1919
```
2020

21-
**Note:** This plugin requires `htmlhint` __version__ or later.
21+
1. If you are using `nvm` and `zsh`, ensure that the line to load `nvm` is in `.zshenv` and not `.zshrc`.
22+
23+
**Note:** This plugin requires `htmlhint` 0.9.0 or later.
2224

2325
### Linter configuration
2426
In order for `htmlhint` 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”](http://sublimelinter.readthedocs.org/en/latest/troubleshooting.html#finding-a-linter-executable) through “Validating your PATH” in the documentation.

0 commit comments

Comments
 (0)